DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, konstantin.ananyev@intel.com,
	ferruh.yigit@intel.com, john.griffin@intel.com,
	fiona.trahe@intel.com
Subject: Re: [dpdk-dev] [PATCH 0/4] minor cleanup of filenames and deps
Date: Thu, 31 Aug 2017 23:03:52 +0200	[thread overview]
Message-ID: <11396382.xjMhZrafoF@xps> (raw)
In-Reply-To: <3102255.qYLVZAutG1@xps>

31/08/2017 17:26, Thomas Monjalon:
> 31/08/2017 16:34, Bruce Richardson:
> > On Thu, Aug 31, 2017 at 03:15:05PM +0100, Ferruh Yigit wrote:
> > > On 8/31/2017 2:42 PM, Bruce Richardson wrote:
> > > > While working on a build system replacement, I find a number of small
> > > > inconsistencies and minor issues with our current code, which, if fixed
> > > > would make it simplier to generalize DPDK build rules. Main set of changes
> > > > is to have the name of the version.map file for libs/drivers consistent
> > > > with the component name - especially in cases where the directory name and
> > > > component name differ slightly.
> > > > 
> > > > NOTE: this patchset is not meant to cover all instances of filename cleanup,
> > > > it just covers the instances I've encountered thus far. Any other instances
> > > > can be fixed as necessary as drivers are being "mesonified" [1].
> > > > 
> > > > [1] http://www.gocomics.com/calvinandhobbes/1993/01/25 :-)
> > > > 
> > > > Bruce Richardson (4):
> > > >   ip_frag: change map filename to standardized value
> > > >   net/ring: change map filename to standardized value
> > > >   ether: rename version file to match library name
> > > >   crypto/qat: remove dependency on ether library
> > > 
> > > Series Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
> > 
> > Hi Thomas,
> > 
> > while these patches are mainly to enable my meson build work, it would
> > be easier for me, I think, if they could be applied on the main tree
> > directly, rather than going through the "next" tree. That way the
> > content on my tree is solely build-system related.
> > 
> > Is that ok with you?
> 
> Yes OK

Applied, thanks

      reply	other threads:[~2017-08-31 21:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31 13:42 Bruce Richardson
2017-08-31 13:42 ` [dpdk-dev] [PATCH 1/4] ip_frag: change map filename to standardized value Bruce Richardson
2017-08-31 13:42 ` [dpdk-dev] [PATCH 2/4] net/ring: " Bruce Richardson
2017-08-31 13:42 ` [dpdk-dev] [PATCH 3/4] ether: rename version file to match library name Bruce Richardson
2017-08-31 14:18   ` Ferruh Yigit
2017-08-31 14:32     ` Bruce Richardson
2017-08-31 13:42 ` [dpdk-dev] [PATCH 4/4] crypto/qat: remove dependency on ether library Bruce Richardson
2017-08-31 14:15 ` [dpdk-dev] [PATCH 0/4] minor cleanup of filenames and deps Ferruh Yigit
2017-08-31 14:34   ` Bruce Richardson
2017-08-31 15:26     ` Thomas Monjalon
2017-08-31 21:03       ` Thomas Monjalon [this message]

Reply instructions:

You may reply publicly 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=11396382.xjMhZrafoF@xps \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=fiona.trahe@intel.com \
    --cc=john.griffin@intel.com \
    --cc=konstantin.ananyev@intel.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).