dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Neil Horman <nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH 08/10] bsd/mk: use the Q variable instead of @ for quiet commands
Date: Fri, 25 Apr 2014 16:18:53 +0200	[thread overview]
Message-ID: <9939700.W9nlxzI1Oh@xps13> (raw)
In-Reply-To: <20140425131912.GD14074-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>

2014-04-25 09:19, Neil Horman:
> On Fri, Apr 25, 2014 at 01:59:46PM +0200, Olivier Matz wrote:
> > This allows to use V=1 to be more verbose to debug the build process
> > of a bsd kernel module.
> > 
> > Signed-off-by: Olivier Matz <olivier.matz-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
> 
> This doesnt seem like it should really be part of this series, given that
> everything else in it is here to fix build breaks.  Nothing wrong with it
> that I can see, but should probably be posted independently.

It fixes verbose compilation mode. So I think it is in the right place in this 
thread (thanks Olivier for the beer ;).

Anyway,
Acked-by: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>

As it is a fix and it's not a big design change, it should go in 1.6.0r2.

-- 
Thomas

  parent reply	other threads:[~2014-04-25 14:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25 11:59 [PATCH 00/10] bsd: fix compilation Olivier Matz
     [not found] ` <1398427188-14914-1-git-send-email-olivier.matz-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-04-25 11:59   ` [PATCH 01/10] bsd/pci: rename device and driver lists Olivier Matz
2014-04-25 11:59   ` [PATCH 02/10] bsd/devargs: introduce API and test Olivier Matz
2014-04-25 11:59   ` [PATCH 03/10] bsd/devargs: use devargs for vdev and PCI whitelist/blacklist Olivier Matz
2014-04-25 11:59   ` [PATCH 04/10] bsd/devargs: use a comma instead of semicolon to separate key/values Olivier Matz
2014-04-25 11:59   ` [PATCH 05/10] bsd/devargs: replace --use-device option by --pci-whitelist and --vdev Olivier Matz
2014-04-25 11:59   ` [PATCH 06/10] bsd/devargs: allow to provide arguments per pci device Olivier Matz
2014-04-25 11:59   ` [PATCH 07/10] bsd/nic_uio: fix module compilation with freebsd 10 Olivier Matz
2014-04-25 11:59   ` [PATCH 08/10] bsd/mk: use the Q variable instead of @ for quiet commands Olivier Matz
     [not found]     ` <1398427188-14914-9-git-send-email-olivier.matz-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-04-25 13:19       ` Neil Horman
     [not found]         ` <20140425131912.GD14074-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2014-04-25 14:18           ` Thomas Monjalon [this message]
2014-04-25 11:59   ` [PATCH 09/10] bsd/mem: get hugepages config Olivier Matz
2014-04-25 11:59   ` [PATCH 10/10] bsd/mem: get physical address of any pointer Olivier Matz
2014-04-25 13:27   ` [PATCH 00/10] bsd: fix compilation Neil Horman
     [not found]     ` <20140425132754.GE14074-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2014-04-29 23:37       ` Thomas Monjalon

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=9939700.W9nlxzI1Oh@xps13 \
    --to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
    /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).