All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian Daudt" <csd@broadcom.com>
To: "Stephen Warren" <swarren@wwwdotorg.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	arm@kernel.org, linux-mtd@lists.infradead.org,
	"JD \(Jiandong\) Zheng" <jdzheng@broadcom.com>,
	Olof Johansson <olof@lixom.net>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] ARM: Remove bcmring NAND driver
Date: Wed, 12 Sep 2012 11:39:20 -0700	[thread overview]
Message-ID: <5050D6D8.8090605@broadcom.com> (raw)
In-Reply-To: <5050C56C.8070603@wwwdotorg.org>

On 12-09-12 10:25 AM, Stephen Warren wrote:
> On 09/12/2012 02:16 AM, Christian Daudt wrote:
>> This driver is being removed as part of the cleanup of the bcmring
>> SoC from mainline as it is no longer maintained.
>>   arch/arm/configs/bcmring_defconfig |    2 -
> Out of curiosity, if you're removing the whole thing, why edit the
> defconfig at all; just delete it instead in whatever patch removes the
> arch/arm parts?
>
I figured it'd be better to remove the config portion on this patch so 
it is self-contained - just in case the other patch gets held up for 
some reason then this one can still be applied and no junk would be left 
around. But agreed - it doesn't really affect things either way.


  thanks,
    Christian.

WARNING: multiple messages have this Message-ID (diff)
From: csd@broadcom.com (Christian Daudt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: Remove bcmring NAND driver
Date: Wed, 12 Sep 2012 11:39:20 -0700	[thread overview]
Message-ID: <5050D6D8.8090605@broadcom.com> (raw)
In-Reply-To: <5050C56C.8070603@wwwdotorg.org>

On 12-09-12 10:25 AM, Stephen Warren wrote:
> On 09/12/2012 02:16 AM, Christian Daudt wrote:
>> This driver is being removed as part of the cleanup of the bcmring
>> SoC from mainline as it is no longer maintained.
>>   arch/arm/configs/bcmring_defconfig |    2 -
> Out of curiosity, if you're removing the whole thing, why edit the
> defconfig at all; just delete it instead in whatever patch removes the
> arch/arm parts?
>
I figured it'd be better to remove the config portion on this patch so 
it is self-contained - just in case the other patch gets held up for 
some reason then this one can still be applied and no junk would be left 
around. But agreed - it doesn't really affect things either way.


  thanks,
    Christian.

  reply	other threads:[~2012-09-12 18:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12  8:16 [PATCH 1/3] ARM: Remove bcmring NAND driver Christian Daudt
2012-09-12  8:16 ` Christian Daudt
2012-09-12  9:51 ` Will Deacon
2012-09-12  9:51   ` Will Deacon
2012-09-12  9:57   ` Russell King - ARM Linux
2012-09-12  9:57     ` Russell King - ARM Linux
2012-09-12 15:17     ` Christian Daudt
2012-09-12 15:17       ` Christian Daudt
2012-09-12 17:25 ` Stephen Warren
2012-09-12 17:25   ` Stephen Warren
2012-09-12 18:39   ` Christian Daudt [this message]
2012-09-12 18:39     ` Christian Daudt
2012-09-12 18:55     ` Olof Johansson
2012-09-12 18:55       ` Olof Johansson

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=5050D6D8.8090605@broadcom.com \
    --to=csd@broadcom.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=jdzheng@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=olof@lixom.net \
    --cc=swarren@wwwdotorg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.