From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Joe Perches <joe@perches.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] declance: Fix 64-bit compilation warnings
Date: Sat, 5 Jul 2014 21:25:52 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.11.1407052103130.15455@eddie.linux-mips.org> (raw)
In-Reply-To: <1404585099.6384.53.camel@joe-AO725>
On Sat, 5 Jul 2014, Joe Perches wrote:
> > > I don't think %#p is valid so it
> > > shouldn't have been set by #.
> >
> > Huh? As recently as last Wednesday you pointed me at the specific commit
> > from Grant that made it valid (GCC format complaints aside).
>
> Those gcc complaints are precisely the thing
> that makes it invalid.
So enforce that in code then, clear the SPECIAL flag where appropriate
and do not try to handle it in one place while leaving other ones to
behave randomly (i.e. a supposedly fixed field width varies depending on
the two uppermost digits). Please note that it's only your proposed
change that introduces that randomness, right now code does what's
supposed and documented to, except a bit inconsistently.
> I believe you're tilting at windmills.
>
> Hey, it works sometimes. Knock yourself out.
I pointed out an inconsistency with the intent to propose a fix once a
consensus have been reached, one way or another. And I think shifting the
inconsistency to a different place, which is what your proposal does,
isn't really a complete solution, although I do recognise the improvement.
Maciej
next prev parent reply other threads:[~2014-07-05 20:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.11.1406290246120.15455@eddie.linux-mips.org>
[not found] ` <20140702.182807.1245632778216212860.davem@davemloft.net>
[not found] ` <alpine.LFD.2.11.1407030244230.15455@eddie.linux-mips.org>
[not found] ` <alpine.LFD.2.11.1407030331550.15455@eddie.linux-mips.org>
[not found] ` <1404356734.14741.18.camel@joe-AO725>
[not found] ` <alpine.LFD.2.11.1407030423300.15455@eddie.linux-mips.org>
[not found] ` <1404364565.14741.26.camel@joe-AO725>
[not found] ` <alpine.LFD.2.11.1407030637030.15455@eddie.linux-mips.org>
[not found] ` <1404368746.14741.36.camel@joe-AO725>
2014-07-05 14:56 ` Maciej W. Rozycki
2014-07-05 16:07 ` Joe Perches
2014-07-05 17:39 ` Maciej W. Rozycki
2014-07-05 18:08 ` Joe Perches
2014-07-05 18:20 ` Maciej W. Rozycki
2014-07-05 18:31 ` Joe Perches
2014-07-05 20:25 ` Maciej W. Rozycki [this message]
2014-07-05 20:45 ` [PATCH] vsprintf: Remove SPECIAL from pointer types Joe Perches
2014-07-06 11:44 ` Maciej W. Rozycki
2014-07-06 14:32 ` Joe Perches
2014-07-07 8:26 ` David Laight
2014-07-07 13:26 ` Joe Perches
2014-07-07 12:01 ` [PATCH v2] declance: Fix 64-bit compilation warnings Grant Likely
2014-07-07 12:18 ` Maciej W. Rozycki
2014-07-07 13:40 ` Joe Perches
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=alpine.LFD.2.11.1407052103130.15455@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=davem@davemloft.net \
--cc=grant.likely@secretlab.ca \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®