From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Greg KH <gregkh@suse.de>, Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux@arm.linux.org.uk,
plagnioj@jcrosoft.com, linux@maxim.org.za,
linux-arm-kernel@lists.infradead.org, patrice.vilchez@atmel.com
Subject: Re: [PATCH RFC] ARM: at91: removal of CAP9 SoC family
Date: Fri, 13 Jan 2012 20:12:53 +0100 [thread overview]
Message-ID: <4F108235.80104@atmel.com> (raw)
In-Reply-To: <20120113181637.GA30300@suse.de>
On 01/13/2012 07:16 PM, Greg KH :
> On Fri, Jan 13, 2012 at 12:10:47PM +0100, Nicolas Ferre wrote:
>> On 01/06/2012 04:33 PM, Nicolas Ferre :
>>> Atmel CAP9 family is not maintained well and products may be
>>> difficult to find now. It will allow to save workforce and
>>> remove LOC during current cleanup process.
>>>
>>> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>>> ---
>>> Documentation/feature-removal-schedule.txt | 14 ++++++++++++++
>>> 1 files changed, 14 insertions(+), 0 deletions(-)
>>
>> Hi Andrew, Greg,
>>
>> Can you please take this patch or is somebody else in charge of this file?
>
> Why wouldn't the maintainers of the feature you are saying is going away
> be the ones responsible for submitting this?
Actually, I am the guy ;-)
>> It it is going to mainline through you, can you add also:
>>
>> Acked-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
>>
>> Or tell me to resend a complete patch.
>>
>> Thanks for your help, best regards,
>>
>>
>>> diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
>>> index 3d84912..23dfea5 100644
>>> --- a/Documentation/feature-removal-schedule.txt
>>> +++ b/Documentation/feature-removal-schedule.txt
>>> @@ -551,3 +551,17 @@ When: 3.5
>>> Why: The iwlagn module has been renamed iwlwifi. The alias will be around
>>> for backward compatibility for several cycles and then dropped.
>>> Who: Don Fry <donald.h.fry@intel.com>
>>> +
>>> +----------------------------
>>> +
>>> +What: The CAP9 SoC family will be removed
>>> +When: 3.4
>>> +Files: arch/arm/mach-at91/at91cap9.c
>>> + arch/arm/mach-at91/at91cap9_devices.c
>>> + arch/arm/mach-at91/include/mach/at91cap9.h
>>> + arch/arm/mach-at91/include/mach/at91cap9_matrix.h
>>> + arch/arm/mach-at91/include/mach/at91cap9_ddrsdr.h
>>> + arch/arm/mach-at91/board-cap9adk.c
>>> +Why: The code is not actively maintained and platforms are now hard to find.
>>> +Who: Nicolas Ferre <nicolas.ferre@atmel.com>
>>> + Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
>
> Ok, why not send this through the ARM tree? Why need me and Andrew?
Ok, I though there was a special procedure for this file. I will queue
this one in arm-soc tree.
Thanks, best regards,
--
Nicolas Ferre
prev parent reply other threads:[~2012-01-13 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 15:33 [PATCH RFC] ARM: at91: removal of CAP9 SoC family Nicolas Ferre
2012-01-07 11:14 ` Jean-Christophe PLAGNIOL-VILLARD
2012-01-13 11:10 ` Nicolas Ferre
2012-01-13 18:16 ` Greg KH
2012-01-13 19:12 ` Nicolas Ferre [this message]
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=4F108235.80104@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@maxim.org.za \
--cc=patrice.vilchez@atmel.com \
--cc=plagnioj@jcrosoft.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;
as well as URLs for NNTP newsgroup(s).