From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Daniel Mack <daniel@zonque.org>, Arnd Bergmann <arnd@arndb.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Mark Brown <broonie@kernel.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>
Subject: Re: [PATCH v3] ARM: pxa: remove Intel Imote2 and Stargate 2 boards
Date: Thu, 03 Mar 2022 22:27:32 +0100 [thread overview]
Message-ID: <874k4eengb.fsf@belgarion.home> (raw)
In-Reply-To: <20220227195653.4dea5045@jic23-huawei> (Jonathan Cameron's message of "Sun, 27 Feb 2022 19:56:53 +0000")
Jonathan Cameron <jic23@kernel.org> writes:
> On Mon, 21 Feb 2022 10:05:31 +0100
> Daniel Mack <daniel@zonque.org> wrote:
>
>> On 2/21/22 08:42, Arnd Bergmann wrote:
>> > On Sun, Feb 20, 2022 at 7:31 PM Jonathan Cameron <jic23@kernel.org> wrote:
>> >>
>> >> From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>> >>
>> >> I have no reason to believe these boards have any more users and I
>> >> haven't tested them for several years. Removing them may simplify
>> >> other changes to the various PXA boards people still care about.
>> >> The recent conversion of pxa2xx_spi to GPIO descriptors for example
>> >> had to update this board despite no one caring or testing.
>> >>
>> >> Great boards that got me started in kernel development, RIP!
>> >>
>> >> Acked-by: Mark Brown <broonie@kernel.org>
>> >> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>> >> Cc: Robert Jarzmik <robert.jarzmik@free.fr>
>> >> Cc: Daniel Mack <daniel@zonque.org>
>> >> Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
>> >> Link: https://lore.kernel.org/r/20210614165720.898792-1-jic23@kernel.org
>>
>> Acked-by: Daniel Mack <daniel@zonque.org>
Acked-by: Robert Jarzmik <robert.jarzmik@free.fr>
>> > I rarely get any pull requests from the PXA maintainers these days, so
>> > I'm not sure how actively they are following the patches. If nobody
>> > picks it up or has any other comments in the next week, can you send
>> > it to soc@kernel.org directly?
>> Pull requests were done by Robert in the past, but I haven't heard from
>> him lately either. Could you take them to your tree directly, Arnd?
Well, there are ... almost no patches to follow, so unless I'm asked to, I would
be pretty happy if this patch flows directly to soc@kernel.org. I'll remake pull
requests if the flow of patches rises, which I doubt a bit.
Cheers.
--
Robert
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-03-03 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 18:31 [PATCH v3] ARM: pxa: remove Intel Imote2 and Stargate 2 boards Jonathan Cameron
2022-02-21 7:42 ` Arnd Bergmann
2022-02-21 9:05 ` Daniel Mack
2022-02-27 19:56 ` Jonathan Cameron
2022-03-03 21:27 ` Robert Jarzmik [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=874k4eengb.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=Jonathan.Cameron@huawei.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).