From: Hans-Christian Noren Egtvedt <egtvedt@samfundet.no>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Boris Brezillon <boris.brezillon@free-electrons.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Haavard Skinnemoen <hskinnemoen@gmail.com>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC] remove support for AVR32 architecture
Date: Tue, 2 May 2017 10:12:11 +0200 [thread overview]
Message-ID: <20170502081211.GA15064@samfundet.no> (raw)
In-Reply-To: <CAHp75Vc2xq65gHh4Es2vcmeHB+MVeidD10JwmqP5raeweMjfig@mail.gmail.com>
Around Tue 02 May 2017 10:46:58 +0300 or thereabout, Andy Shevchenko wrote:
> On Tue, May 2, 2017 at 8:52 AM, Hans-Christian Noren Egtvedt
> <egtvedt@samfundet.no> wrote:
>> Around Mon 27 Mar 2017 15:35:56 +0200 or thereabout, Hans-Christian Noren Egtvedt wrote:
>>> Around Mon 27 Mar 2017 15:26:04 +0200 or thereabout, Boris Brezillon wrote:
>>>> On Wed, 1 Mar 2017 21:44:26 +0100 Hans-Christian Noren Egtvedt <egtvedt@samfundet.no> wrote:
>>
>> <snipp AVR32 removal discussion>
>>
>>>> Is this still planned for 4.12?
>>>
>>> Yes, I have received no objections, only feedback to bits and pieces in
>>> generic areas that can be removed in addition to my initial patch.
>>
>> Linus has merged the branch removing AVR32 architecture now.
>
> Thanks!
>
> Question: does it make sense / needed to Cc you on patches that are
> going to remove AVR32 (related) bits in individual drivers? I suppose
> I will do Cc you.
I do have a series already prepared at
https://git.kernel.org/pub/scm/linux/kernel/git/egtvedt/linux-avr32.git/log/?h=avr32-cleanup
It does not touch DMA and Ethernet parts though.
--
Hans-Christian Noren Egtvedt
next prev parent reply other threads:[~2017-05-02 8:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 20:44 [RFC] remove support for AVR32 architecture Hans-Christian Noren Egtvedt
2017-03-01 21:43 ` Andy Shevchenko
2017-03-01 21:55 ` Boris Brezillon
2017-03-02 15:55 ` Nicolas Ferre
2017-03-06 5:58 ` Håvard Skinnemoen
2017-03-06 19:07 ` Hans-Christian Noren Egtvedt
2017-03-27 13:26 ` Boris Brezillon
2017-03-27 13:35 ` Hans-Christian Noren Egtvedt
2017-05-02 5:52 ` Hans-Christian Noren Egtvedt
2017-05-02 7:46 ` Andy Shevchenko
2017-05-02 8:12 ` Hans-Christian Noren Egtvedt [this message]
2017-05-02 8:33 ` Andy Shevchenko
2017-05-02 11:27 ` Andy Shevchenko
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=20170502081211.GA15064@samfundet.no \
--to=egtvedt@samfundet.no \
--cc=andy.shevchenko@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=hskinnemoen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=torvalds@linux-foundation.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