linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
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 13:29:57 +0200	[thread overview]
Message-ID: <CACRpkdbEiLfONF_=RAonyJCdgzOPo2BQuaeu1SxZgSn1qt8rog@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a2fXtAHJL7-Qs0dm3fwjFn0NvmotfpeW2zUOqh9ymK2cw@mail.gmail.com>

On Mon, Jul 11, 2022 at 12:44 PM Arnd Bergmann <arnd@arndb.de> wrote:
> On Mon, Jul 11, 2022 at 10:11 AM Linus Walleij <linus.walleij@linaro.org> wrote:

> > two patches deleting two unmainatined DaVinci boards.
(...)
> 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?

Tag is updated like this:

The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:

  Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git
tags/davinci-boards-delete-v5.20

for you to fetch changes up to b4aed01de48652928c8299f793625936f14d1739:

  ARM: davinci: Delete DM646x board files (2022-07-01 14:10:20 +0200)

----------------------------------------------------------------
Delete the two DaVinci board families DM644x and DM646x.

The reason why I'm pushing for this is that I have floated
patches to update the board files to use GPIO descriptors,
iterated and fixed bugs in the patches reported by reviewers
and build robots, and then the patches have not been merged.
See:

v6:
https://lore.kernel.org/linux-arm-kernel/20201103000158.325147-1-linus.walleij@linaro.org/
https://lore.kernel.org/linux-arm-kernel/20210715191141.430307-3-linus.walleij@linaro.org/

v7:
https://lore.kernel.org/linux-arm-kernel/20220507124536.171930-1-linus.walleij@linaro.org/
https://lore.kernel.org/linux-arm-kernel/20220507124536.171930-2-linus.walleij@linaro.org/

I assume this is not getting merged because of lack of interest
in the platform, and such things happen. To save myself and
others from spending work hours on maintaining and modernizing
a platform that is not used, delete the board files.

----------------------------------------------------------------
Linus Walleij (2):
      ARM: davinci: Delete DM644x board files
      ARM: davinci: Delete DM646x board files

Yours,
Linus Walleij

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2022-07-11 11:31 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
2022-07-11 11:29   ` Linus Walleij [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='CACRpkdbEiLfONF_=RAonyJCdgzOPo2BQuaeu1SxZgSn1qt8rog@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=brgl@bgdev.pl \
    --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).