From: Arnd Bergmann <arnd@arndb.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: SoC Team <soc@kernel.org>, arm-soc <arm@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Sekhar Nori <nsekhar@ti.com>,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [GIT PULL] Delete two DaVinci boards
Date: Mon, 11 Jul 2022 12:44:10 +0200 [thread overview]
Message-ID: <CAK8P3a2fXtAHJL7-Qs0dm3fwjFn0NvmotfpeW2zUOqh9ymK2cw@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdZh8GdZzGsJ=h_E8RPgAHX8HqXs1871w95TVZD0SXHbkA@mail.gmail.com>
On Mon, Jul 11, 2022 at 10:11 AM Linus Walleij <linus.walleij@linaro.org> wrote:
>
> Hi SoC folks,
>
> two patches deleting two unmainatined DaVinci boards.
> The patches describe how I tried to update these boards
> but there is no interest in that so now I am deleting them
> as unused and unmaintained,
>
> Please pull it in unless the DaVinci maintainers step in
> and says no.
I'll give them a few days to reply. In the discussion about deprecating
board files we already decided that only the DT-based davinci
machines are really needed, so I don't expect much objection to
removing them now, but otherwise they are going away in six months
anyway.
Your git tag description however needs a little more background,
I don't want to pull this and bypass the maintainers with a one-line
commit text. Can you update the tag to describe more about why
speeding up the removal is important to you?
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-07-11 10:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 8:11 [GIT PULL] Delete two DaVinci boards Linus Walleij
2022-07-11 10:44 ` Arnd Bergmann [this message]
2022-07-11 11:29 ` Linus Walleij
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=CAK8P3a2fXtAHJL7-Qs0dm3fwjFn0NvmotfpeW2zUOqh9ymK2cw@mail.gmail.com \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nsekhar@ti.com \
--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).