From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/5] mfd: remove obsolete ti-ssp driver
Date: Wed, 26 Feb 2014 22:00:04 +0000 [thread overview]
Message-ID: <20140226220004.GQ9195@lee--X1> (raw)
In-Reply-To: <20140226205703.GA21483@n2100.arm.linux.org.uk>
> > > The tnetv107x platform is getting removed, so this driver
> > > is not needed any more.
> > >
> > > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> > > Cc: Samuel Ortiz <sameo@linux.intel.com>
> > > Cc: Lee Jones <lee.jones@linaro.org>
> > > ---
> > > drivers/mfd/Kconfig | 11 --
> > > drivers/mfd/Makefile | 1 -
> > > drivers/mfd/ti-ssp.c | 465 ---------------------------------------------------
> > > 3 files changed, 477 deletions(-)
> > > delete mode 100644 drivers/mfd/ti-ssp.c
> >
> > Applied, thanks.
>
> This makes me wonder whether you apply any patch you receive via email,
> or whether you read the covering email first.
I did (miss-)read the cover letter first.
> Arnd's 0/5 email said:
>
> However, I'm looking for an Ack from
> Cyril Chemparathy and Sekhar Nori first, to be sure we
> won't need this code in the future.
I read this to mean "looking for an Ack from Cyril and Sekhar for
patches which are due to go in via a different tree (ARM-SoC?)".
My apologies for misreading. Patch removed from MFD -next until I get
a further nod.
> This is exactly the reason why I'd now recommend that if people want to
> send out patches which they don't intend maintainers to take, that they
> use "[PATCH RFC" in the subject _and_ they make sure that the patch can't
> be trivially applied. That means maintainers have to (a) not notice the
> RFC in the subject, and _then_ they have to intentionally fix the patch
> before applying. Both taken together will be sufficient deterrent for
> this kind of mistake happening.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-02-26 22:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 12:43 [PATCH 0/5] ARM: davinci: tnetv107x removal Arnd Bergmann
2014-02-26 12:43 ` [PATCH 1/5] ARM: davinci: remove tnetv107x support Arnd Bergmann
2014-02-26 14:44 ` Kevin Hilman
2014-02-26 12:43 ` [PATCH 2/5] gpio: remove obsolete tnetv107x driver Arnd Bergmann
2014-03-05 1:52 ` Linus Walleij
2014-03-05 2:45 ` Linus Walleij
2014-02-26 12:43 ` [PATCH 3/5] spi: remove obsolete spi-ti-ssp driver Arnd Bergmann
2014-03-03 6:38 ` Mark Brown
2014-02-26 12:43 ` [PATCH 4/5] mfd: remove obsolete ti-ssp driver Arnd Bergmann
2014-02-26 12:51 ` Lee Jones
2014-02-26 20:57 ` Russell King - ARM Linux
2014-02-26 22:00 ` Lee Jones [this message]
2014-02-26 12:43 ` [PATCH 5/5] input: remove obsolete tnetv107x drivers Arnd Bergmann
2014-02-26 13:46 ` [PATCH 0/5] ARM: davinci: tnetv107x removal Arnd Bergmann
2014-02-26 20:04 ` Sergei Shtylyov
2014-02-27 13:37 ` Sekhar Nori
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=20140226220004.GQ9195@lee--X1 \
--to=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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