All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Noren Egtvedt <egtvedt@samfundet.no>
To: "Håvard Skinnemoen" <hskinnemoen@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Nicolas Ferre <nicolas.ferre@atmel.com>,
	Boris Brezillon <boris.brezillon@free-electrons.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC] remove support for AVR32 architecture
Date: Mon, 6 Mar 2017 20:07:19 +0100	[thread overview]
Message-ID: <20170306190718.GA21771@samfundet.no> (raw)
In-Reply-To: <CACiLriQoPM=O4q916Bo_7Uq7+V8yKOSeAiy1Yvf9oh7iBz9jsQ@mail.gmail.com>

Around Sun 05 Mar 2017 21:58:16 -0800 or thereabout, Håvard Skinnemoen wrote:
> On Wed, Mar 1, 2017 at 12:44 PM, Hans-Christian Noren Egtvedt
> <egtvedt@samfundet.no> wrote:
>> I have prepared three patches in my for-linus branch in git tree
>> https://git.kernel.org/cgit/linux/kernel/git/egtvedt/linux-avr32.git
> 
> Acked-by: Haavard Skinnemoen <hskinnemoen@gmail.com>
> 
> Thank you for keeping it alive for so long!
> 
> I looked through you tree superficially. There are a few references to
> AVR32 remaining. Most of them are for other subsystems, but you could
> consider picking up a couple of more for your patchset:
> 
> include/uapi/linux/elf-em.h still defines EM_AVR32. This could be
> considered a part of the architecture code.

My git grep magic did not catch this.

> lib/Kconfig.debug has a list of architectures which want frame
> pointers. You could probably remove AVR32 from that list.

Same.

Will add a patch for these two.

> mm/Kconfig has a special case for AVR32 needing two quicklists.
>

This one I have in a different series, the one I planned to push to various
maintainers after the initial removal.

> If you were planning to patch each of those separately later, please
> ignore my comments.

Partly (-:

-- 
mvh
Hans-Christian Noren Egtvedt

  reply	other threads:[~2017-03-06 19:51 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 [this message]
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
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=20170306190718.GA21771@samfundet.no \
    --to=egtvedt@samfundet.no \
    --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 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.