archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <>
To: Linus Walleij <>,
	arm-soc <>, SoC Team <>
Cc: Arnd Bergmann <>, Imre Kaloz <>,
	Zoltan HERPAI <>,
	Linux ARM <>
Subject: Re: [GIT PULL] Delete IXP4xx boardfiles replaced by device trees
Date: Wed, 18 Aug 2021 15:43:21 +0200	[thread overview]
Message-ID: <> (raw)
Message-ID: <20210818134321.wbygnqiqRwasy_6pGLskNrA0OseyICSLTxJKtFg1EH4@z> (raw)
In-Reply-To: <>

From: Arnd Bergmann <>

On Fri, 13 Aug 2021 15:14:01 +0200, Linus Walleij wrote:
> this concludes the first big chunk of IXP4xx cleanup and DT conversion
> by deleting a majority of the boardfiles now supported by the device
> trees.
> The details of which boardfiles are deleted and the two that are kept can
> be found below. The idea is that all devices except the Omicron ones
> will keep being supported, but as device trees. Omicron has publicly
> stated that they have no interest in keeping supporting the boards,
> if someone anyway steps up and need them, scratch device trees
> exist on the mailing list.
> [...]

Merged into arm/soc, thanks!

merge commit: 0fbd7409446a8ee76ee701ec846ede917c6c89fa


linux-arm-kernel mailing list

  parent reply	other threads:[~2021-08-18 13:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-13 13:14 [GIT PULL] Delete IXP4xx boardfiles replaced by device trees Linus Walleij
2021-08-13 13:14 ` Linus Walleij
     [not found] ` <20210818134321.wbygnqiqRwasy_6pGLskNrA0OseyICSLTxJKtFg1EH4@z>
2021-08-18 13:43   ` Arnd Bergmann [this message]
2021-08-18 13:50 ` patchwork-bot+linux-soc

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \

* 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).