From: Mark Brown <broonie@kernel.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
patches@opensource.cirrus.com
Subject: Re: [PATCH] ARM: pxa: remove Intel Imote2 and Stargate 2 boards
Date: Mon, 24 May 2021 09:40:36 +0100 [thread overview]
Message-ID: <20210524084036.GC4318@sirena.org.uk> (raw)
In-Reply-To: <20210523163606.1966355-1-jic23@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 708 bytes --]
On Sun, May 23, 2021 at 05:36:06PM +0100, Jonathan Cameron 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.
Acked-by: Mark Brown <broonie@kernel.org>
> Note this is (I think) the only user of sound/soc/wm8940 in mainline.
> Mark/Liam/Cirrus folks, would it be helpful to remove that as well?
> Happy to send a follow up patch if desired.
No, there's generally no reason to remove CODEC drivers - they require
very little overhead and there may be out of tree users.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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:[~2021-05-24 22:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 16:36 [PATCH] ARM: pxa: remove Intel Imote2 and Stargate 2 boards Jonathan Cameron
2021-05-24 8:40 ` Mark Brown [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=20210524084036.GC4318@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=jic23@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=patches@opensource.cirrus.com \
--cc=robert.jarzmik@free.fr \
/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).