From: Brian Norris <computersforpeace@gmail.com>
To: Mark Brown <broonie@debian.org>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
"David Woodhouse" <David.Woodhouse@intel.com>,
"Artem Bityutskiy" <dedekind1@gmail.com>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
linux-spi <linux-spi@vger.kernel.org>,
linux-mtd@lists.infradead.org, "Huang Shijie" <shijie8@gmail.com>,
"Ian Campbell" <ijc@hellion.org.uk>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
debian-kernel <debian-kernel@lists.debian.org>,
"Ben Hutchings" <ben@decadent.org.uk>,
linux-arm-kernel@lists.infradead.org,
"Jason Cooper" <jason@lakedaemon.net>
Subject: Re: [PATCH 1/2] mtd: m25p80: get rid of spi_get_device_id
Date: Wed, 1 Oct 2014 11:43:03 -0700 [thread overview]
Message-ID: <20141001184303.GX1193@ld-irv-0074> (raw)
In-Reply-To: <20141001182003.GB17974@sirena.org.uk>
On Wed, Oct 01, 2014 at 07:20:03PM +0100, Mark Brown wrote:
> On Mon, Sep 29, 2014 at 11:47:53AM +0200, Rafał Miłecki wrote:
> > This simplifies the way we use spi_nor framework and will allow us to
> > drop spi_nor_match_id.
>
> Please don't CC linux-spi on spi-nor patches that don't have SPI level
> changes, it just clogs up patchwork.
+1 from me. I appreciate the converse, as I don't need unrelated noise
on linux-mtd.
(I feel sorry for people over at linux-arm-kernel and devicetree, since
they get CC'd on a large variety of unrelated things, it seems. I'm sure
the firehose gets to be almost as bad as LKML sometimes.)
Brian
next prev parent reply other threads:[~2014-10-01 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 9:47 [PATCH 1/2] mtd: m25p80: get rid of spi_get_device_id Rafał Miłecki
2014-09-29 9:47 ` [PATCH 2/2] mtd: spi-nor: make spi_nor_scan() take a chip type name, not spi_device_id Rafał Miłecki
2014-10-17 16:31 ` Brian Norris
2014-10-01 18:20 ` [PATCH 1/2] mtd: m25p80: get rid of spi_get_device_id Mark Brown
2014-10-01 18:43 ` Brian Norris [this message]
2014-10-01 19:24 ` Rafał Miłecki
2014-10-17 16:30 ` Brian Norris
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=20141001184303.GX1193@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=David.Woodhouse@intel.com \
--cc=andrew@lunn.ch \
--cc=ben@decadent.org.uk \
--cc=broonie@debian.org \
--cc=debian-kernel@lists.debian.org \
--cc=dedekind1@gmail.com \
--cc=geert@linux-m68k.org \
--cc=hauke@hauke-m.de \
--cc=ijc@hellion.org.uk \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=shijie8@gmail.com \
--cc=zajec5@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