From: "J. Bruce Fields" <bfields@fieldses.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Pavel Emelyanov <xemul@openvz.org>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] Wrap buffers used for rpc debug printks into RPC_IFDEBUG
Date: Thu, 21 Feb 2008 16:58:24 -0500 [thread overview]
Message-ID: <20080221215824.GH13358@fieldses.org> (raw)
In-Reply-To: <1203630322.8258.35.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
On Thu, Feb 21, 2008 at 04:45:22PM -0500, Trond Myklebust wrote:
>
> On Thu, 2008-02-21 at 10:57 +0300, Pavel Emelyanov wrote:
> > Sorry for the noise, but here's the v3 of this compilation fix :)
> >
> > There are some places, which declare the char buf[...] on the stack
> > to push it later into dprintk(). Since the dprintk sometimes (if the
> > CONFIG_SYSCTL=n) becomes an empty do { } while (0) stub, these buffers
> > cause gcc to produce appropriate warnings.
> >
> > Wrap these buffers with RPC_IFDEBUG macro, as Trond proposed, to
> > compile them out when not needed.
> >
> > Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
>
> Thanks Pavel!
Yes, thanks Pavel for persisting--it looks very straightforward to me
this way.
>
> Bruce, do you want to shepherd this in, or should I? I'm planning on
> pushing a couple of bugfixes to Linus this evening anyway...
That would be great; feel free to add an
Acked-by: J. Bruce Fields <bfields@citi.umich.edu>
if you want.
--b.
prev parent reply other threads:[~2008-02-21 21:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 7:57 [PATCH] Wrap buffers used for rpc debug printks into RPC_IFDEBUG Pavel Emelyanov
2008-02-21 21:45 ` Trond Myklebust
[not found] ` <1203630322.8258.35.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-02-21 21:58 ` J. Bruce Fields [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=20080221215824.GH13358@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
--cc=xemul@openvz.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