From: David Laight <david.laight.linux@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Sean Chang <seanwascoding@gmail.com>,
nicolas.ferre@microchip.com, claudiu.beznea@tuxon.dev,
trond.myklebust@hammerspace.com, anna@kernel.org,
netdev@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] sunrpc: fix unused variable warnings by using no_printk
Date: Fri, 27 Feb 2026 18:15:32 +0000 [thread overview]
Message-ID: <20260227181532.1616f720@pumpkin> (raw)
In-Reply-To: <c28cbfc2-208f-47db-9c5a-21b54b2be8c1@lunn.ch>
On Fri, 27 Feb 2026 18:57:33 +0100
Andrew Lunn <andrew@lunn.ch> wrote:
> > > # define ifdebug(fac) if (0)
> > > -# define dfprintk(fac, fmt, ...) do {} while (0)
> > > -# define dfprintk_rcu(fac, fmt, ...) do {} while (0)
> > > +# define dfprintk(fac, fmt, ...) no_printk(fmt, ##__VA_ARGS__)
> > > +# define dfprintk_rcu(fac, fmt, ...) no_printk(fmt, ##__VA_ARGS__)
> >
> > You can omit fmt, then you don't need the ##
> > #define dfprintk(fac, ...) no_printk(__VA_ARGS__)
>
> /*
> * Dummy printk for disabled debugging statements to use whilst maintaining
> * gcc's format checking.
> */
> #define no_printk(fmt, ...) \
> ({ \
> if (0) \
> _printk(fmt, ##__VA_ARGS__); \
> 0; \
> })
>
> Without fmt, gcc cannot do format checking. Or worse, it takes the
> first member of __VA_ARGS__ as the format, and gives spurious errors?
By the time the compiler looks at it the pre-processor has expanded
__VA_ARGS__.
So it doesn't matter that the format string is in the __VA_ARGS__
list rather than preceding it.
David
>
> Andrew
next prev parent reply other threads:[~2026-02-27 18:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 15:26 [PATCH v4 0/2] Fix warnings for RISC-V builds Sean Chang
2026-02-27 15:26 ` [PATCH v4 1/2] sunrpc: fix unused variable warnings by using no_printk Sean Chang
2026-02-27 15:58 ` Chuck Lever
2026-02-27 16:00 ` Andrew Lunn
2026-02-27 17:38 ` David Laight
2026-02-27 17:57 ` Andrew Lunn
2026-02-27 18:15 ` David Laight [this message]
2026-02-28 14:56 ` Sean Chang
2026-02-28 17:23 ` Sean Chang
2026-02-28 20:04 ` Andrew Lunn
2026-03-01 15:40 ` Sean Chang
2026-02-27 15:26 ` [PATCH v4 2/2] net: macb: use ethtool_sprintf to fill ethtool stats strings Sean Chang
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=20260227181532.1616f720@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=andrew@lunn.ch \
--cc=anna@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=seanwascoding@gmail.com \
--cc=trond.myklebust@hammerspace.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.