From: Valdis.Kletnieks@vt.edu
To: Nick Krause <xerofoiffy@gmail.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-spi@vger.kernel.org (open list:SPI SUBSYSTEM),
linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCH 1/1] spi: Remove unused definitions
Date: Wed, 06 Aug 2014 14:27:20 -0400 [thread overview]
Message-ID: <17153.1407349640@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 06 Aug 2014 13:53:17 -0400." <1407347597-2168-1-git-send-email-xerofoiffy@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]
On Wed, 06 Aug 2014 13:53:17 -0400, Nick Krause said:
> Remove unused definition which cause the following warnings
>
> drivers/spi/spi-omap-100k.c:73:0: warning: "WRITE" redefined [enabled by default]
> include/linux/fs.h:193:0: note: this is the location of the previous definition
> drivers/spi/spi-omap-100k.c:74:0: warning: "READ" redefined [enabled by default]
> include/linux/fs.h:192:0: note: this is the location of the previous definition
> -#define WRITE 0
> -#define READ 1
NAK. Full stop. These are potentially used in an inner macro someplace, and by
removing these, the conflicting values from fs.h will be used instead.
#define READ 0
#define WRITE RW_MASK
So if there *is* a use in an inner macro, you just screwed the pooch
and introduced a bug in this "clean up" - somebody will be expecting to see
a 0 for a READ, and will receive a 1 instead. This can't end well.
Nick - how *exactly* did you identify that these are in fact not used?
Given your history of submitting poorly researched patches, you're going to
have to justify the "unused" better than the handwaving you've done here.
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
next prev parent reply other threads:[~2014-08-06 18:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 17:53 [PATCH 1/1] spi: Remove unused definitions Nick Krause
2014-08-06 18:27 ` Valdis.Kletnieks [this message]
2014-08-06 18:35 ` Ilia Mirkin
2014-08-06 18:50 ` Geert Uytterhoeven
2014-08-06 19:34 ` Mark Brown
2014-08-20 20:26 ` Pavel Machek
2014-08-20 21:12 ` Valdis.Kletnieks
2014-08-20 21:56 ` Pavel Machek
2014-08-06 18:33 ` Greg KH
2014-08-06 19:14 ` Guenter Roeck
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=17153.1407349640@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
--cc=xerofoiffy@gmail.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