mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Hans Verkuil" <hverkuil-cisco@xs4all.nl>,
	"Song Chen" <chensong_2000@189.cn>,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH] drivers/media/pci/sta2x11: replace legacy GPIO APIs
Date: Fri, 21 Feb 2025 16:50:18 +0100	[thread overview]
Message-ID: <5b300c49-74b2-45b2-8e2c-79476070c2c7@app.fastmail.com> (raw)
In-Reply-To: <eaf46d30-71a4-4200-b1e1-6b657372f5ef@xs4all.nl>

On Thu, Feb 20, 2025, at 14:43, Hans Verkuil wrote:
> Hi Arnd,
>
> On 12/3/24 08:52, Arnd Bergmann wrote:
>> On Tue, Dec 3, 2024, at 08:48, Song Chen wrote:
>>> ok, then remove it.
>>>
>>> what about drivers/staging/media/atomisp/pci/atomisp_gmin_platform.c,
>>> it has the same problem, are you going to remove it as well?
>> 
>> No, that one is likely to stay around for a while. I think it
>> was actually removed before and brought back because there are
>> users. That one is just the on-chip component on certain Atom
>> SoCs.
>> 
>> The sta2x11 platform was never that widely used and I think might
>> have not been completely upstreamed.
>
> So I can drop this patch, and in the near future I guess we'll receive
> a patch from you removing this driver? Is that correct?

Yes, I have a patch that I am already planning to resend to
drop the sta2x11 platform on x86 along with some more arm32
and x86-32 platforms, followed by a series to remove all of
the orphaned drivers from that round and previous drivers
that got forgotten last time.

     Arnd

      reply	other threads:[~2025-02-21 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03  7:27 Song Chen
2024-12-03  7:32 ` Arnd Bergmann
2024-12-03  7:48   ` Song Chen
2024-12-03  7:52     ` Arnd Bergmann
2025-02-20 13:43       ` Hans Verkuil
2025-02-21 15:50         ` Arnd Bergmann [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=5b300c49-74b2-45b2-8e2c-79476070c2c7@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=chensong_2000@189.cn \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@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

all inboxes | Powered by JetHome®