From: Pavel Roskin <proski@gnu.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] saner warnings for restricted types
Date: Tue, 15 Jan 2008 16:04:47 -0500 [thread overview]
Message-ID: <1200431087.3457.0.camel@dv> (raw)
In-Reply-To: <20080115185856.GT27894@ZenIV.linux.org.uk>
On Tue, 2008-01-15 at 18:58 +0000, Al Viro wrote:
> On Tue, Jan 15, 2008 at 12:36:12PM -0500, Pavel Roskin wrote:
> > On Tue, 2008-01-15 at 16:52 +0000, Al Viro wrote:
> > > if (class & TYPE_RESTRICT) {
> > > - warning(expr->pos, "restricted degrades to integer");
> > > if (class & TYPE_FOULED)
> > > *ctype = unfoul(*ctype);
> > > + warning(expr->pos, "%sdegrades to integer",
> > > + show_typename(*ctype));
> >
> > Missing space after "%s"?
>
> No. Try it and you'll see...
OK, just wanted to make sure. Thanks for the explanation!
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-01-15 21:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 16:52 [PATCH] saner warnings for restricted types Al Viro
2008-01-15 17:36 ` Pavel Roskin
2008-01-15 18:58 ` Al Viro
2008-01-15 21:04 ` Pavel Roskin [this message]
2008-01-15 23:14 ` Al Viro
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=1200431087.3457.0.camel@dv \
--to=proski@gnu.org \
--cc=linux-sparse@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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).