From: patchwork-bot+linux-soc@kernel.org
To: Linus Walleij <linus.walleij@linaro.org>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] Delete IXP4xx boardfiles replaced by device trees
Date: Wed, 18 Aug 2021 13:50:13 +0000 [thread overview]
Message-ID: <162929461364.9396.6814212374930212026.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <CACRpkdY=sPDkzmbmm+0UQnJi7BXZKH14GLmyVwKC+4cLCJpmdA@mail.gmail.com>
Hello:
This pull request was applied to soc/soc.git (refs/heads/for-next):
On Fri, 13 Aug 2021 15:14:01 +0200 you wrote:
> Hi SoC folks,
>
> 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.
>
> [...]
Here is the summary with links:
- [GIT,PULL] Delete IXP4xx boardfiles replaced by device trees
https://git.kernel.org/soc/soc/c/0fbd7409446a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-08-18 13:50 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
2021-08-18 13:50 ` patchwork-bot+linux-soc [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=162929461364.9396.6814212374930212026.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=soc@kernel.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;
as well as URLs for NNTP newsgroup(s).