DPDK CI discussions
 help / color / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jeremy Plsek <jplsek@iol.unh.edu>
Cc: Ali Alnubani <alialnu@mellanox.com>,
	"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
	"ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] [PATCH v4] add script to decide best tree match for patches
Date: Fri, 19 Apr 2019 21:41:03 +0200
Message-ID: <2581335.NoBSEKiLG5@xps> (raw)
In-Reply-To: <CA+xUZB438Op8xex6VZSSukrhWfX24wR7SErwVoehGF1fLw0yRQ@mail.gmail.com>

19/04/2019 20:06, Jeremy Plsek:
> On Fri, Apr 19, 2019 at 1:55 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> > 19/04/2019 19:33, Jeremy Plsek:
> > > I thinks so. Only more patchsets will tell, but that could be improved
> > > after the fact. So I think it's fine to merge it in.
> > >
> > > At first glance, the only part that I don't think is implemented is
> > > mentioned here: https://bugs.dpdk.org/show_bug.cgi?id=166#c35
> > > > We must match the common prefix of the git trees.
> > > > Examples:
> > > > dpdk-next-net-intel + dpdk = dpdk
> > > > dpdk-next-net-intel + dpdk-next-net-mlx = dpdk-next-net
> > > Since some of the patches are being set to dpdk-next-net-mlx instead
> > > of dpdk-next-net. But I'm fine with how it is right now and wouldn't
> > > mind it getting changed to this later on.
> >
> > It is supposed to be fixed.
> > Please could you give an example of a misbehaviour?
> 
> The most recent example is series 4380. For me, that returned dpdk-next-net-mlx.

The series 4380 is mlx only, so it fine to match dpdk-next-net-mlx.
Why do you expect something else?




  reply index

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-12 14:48 [dpdk-ci] [PATCH v2] " Ali Alnubani
2019-02-15 21:28 ` Jeremy Plsek
2019-02-15 23:08   ` Thomas Monjalon
2019-02-17  8:09     ` Ali Alnubani
2019-02-16 16:03 ` [dpdk-ci] [PATCH v3] " Ali Alnubani
2019-04-09 16:12   ` [dpdk-ci] [PATCH v4] " Ali Alnubani
2019-04-18  8:16     ` Ali Alnubani
2019-04-19 16:21       ` Jeremy Plsek
2019-04-19 16:24         ` Thomas Monjalon
2019-04-19 17:33           ` Jeremy Plsek
2019-04-19 17:55             ` Thomas Monjalon
2019-04-19 18:06               ` Jeremy Plsek
2019-04-19 19:41                 ` Thomas Monjalon [this message]
2019-04-19 19:45                   ` Jeremy Plsek
2019-04-19 20:39     ` Thomas Monjalon

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2581335.NoBSEKiLG5@xps \
    --to=thomas@monjalon.net \
    --cc=alialnu@mellanox.com \
    --cc=ci@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jplsek@iol.unh.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK CI discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/ public-inbox