From: Mark Brown <broonie@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>,
Nick Krause <xerofoiffy@gmail.com>,
Richard Weinberger <richard.weinberger@gmail.com>,
"open list:SPI SUBSYSTEM" <linux-spi@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 1/1] spi: Remove unused definitions
Date: Wed, 6 Aug 2014 20:34:53 +0100 [thread overview]
Message-ID: <20140806193453.GJ17528@sirena.org.uk> (raw)
In-Reply-To: <CAMuHMdVJQd0Mb8aXbd9iqkabzKdw9WSR791LxqUoVEJ1g1kaHA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]
On Wed, Aug 06, 2014 at 08:50:15PM +0200, Geert Uytterhoeven wrote:
> To be 100% sure, I tried to find with which kernel config this warning shows up.
> It doesn't happen for omap1_defconfig with CONFIG_SPI_OMAP_100K,
> which was the most likely culprit.
> It does happen with sparc/sparc64 allmodconfig. However, changing or
> removing the READ and WRITE definitions in drivers/spi/spi-omap-100k.c
> doesn't have any influence on the preprocessed source files
> ("make drivers/spi/spi-omap-100k.i", modulo line number changes),
> for both omap1 and sparc builds.
> (Nick: I believe the above is what people really want to see)
> So I conclude they are really not used, and they can be safely removed.
> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
Right, I'd already done the same analysis myself with looking for uses
myself (though I didn't go looking for how to trigger). Nick, please do
look at the analysis Geert provided above - it is indeed exactly the
sort of thing that people would want to see, just saying what's in the
diff isn't enough especially given the well advertised quality problems
with your submissions. You really need to explain why the change you're
making is a good idea.
I've applied the change.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-06 19:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 17:53 Nick Krause
2014-08-06 18:27 ` Valdis.Kletnieks
2014-08-06 18:35 ` Ilia Mirkin
2014-08-06 18:50 ` Geert Uytterhoeven
2014-08-06 19:34 ` Mark Brown [this message]
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=20140806193453.GJ17528@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.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
all inboxes | Powered by JetHome®