linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <lrodriguez@qca.qualcomm.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Julia Lawall <julia@diku.dk>, Jesper Andersen <jespera@gmail.com>,
	linux-wireless@vger.kernel.org, Hauke Mehrtens <hauke@hauke-m.de>
Subject: Re: [PATCH] compat-wireless: avoid pr_fmt build SPAM
Date: Fri, 18 Nov 2011 16:49:18 -0500	[thread overview]
Message-ID: <20111118214917.GA29042@tuxdriver.com> (raw)
In-Reply-To: <CAB=NE6Urei3NSQ05d_4MOUEoBb=tAvy9WE+_5zyc1-j_S+VnDg@mail.gmail.com>

On Fri, Nov 18, 2011 at 01:12:51PM -0800, Luis R. Rodriguez wrote:
> On Fri, Nov 18, 2011 at 1:00 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > On Fri, 2011-11-18 at 15:54 -0500, John W. Linville wrote:
> >> The way the compat-* header files are included causes the default
> >> pr_fmt definition from <linux/kernel.h> to be evaluated for every file.
> >> Files that define pr_fmt then generate a lot of build SPAM about
> >> pr_fmt being redefined.
> >>
> >> Eliminate the build noise by preemptively undefining pr_fmt in those
> >> files that define it.  This is accomplished by adding a patch to the
> >> patches directory.
> >
> > This patch is going to be relatively painful when files move etc -- is
> > that really worth it? I for one will just drop it in our compat version
> > if it goes in since I don't even have all the files it patches :-)
> 
> This may be a good use case for spatch magic?

Yeah, I was thinking exactly that.  I haven't tried spatch yet,
but it would probably handle this fairly well.

Are you using it anywhere else?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2011-11-18 22:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18 20:54 [PATCH] compat-wireless: avoid pr_fmt build SPAM John W. Linville
2011-11-18 21:00 ` Johannes Berg
2011-11-18 21:09   ` John W. Linville
2011-11-18 21:12   ` Luis R. Rodriguez
2011-11-18 21:49     ` John W. Linville [this message]
2011-11-18 22:26 ` Joe Perches
2011-11-18 22:34   ` John W. Linville
2011-11-18 23:03     ` Luis R. Rodriguez
2011-11-18 23:21       ` Hauke Mehrtens

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=20111118214917.GA29042@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=hauke@hauke-m.de \
    --cc=jespera@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=julia@diku.dk \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@qca.qualcomm.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).