linux-kernel - Re: [PATCH 0/4] Remove the wl1273 FM Radio

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250902113527.GB1694@pendragon.ideasonboard.com>
Date: Tue, 2 Sep 2025 13:35:27 +0200
From: Laurent Pinchart <laurent.pinchart@...asonboard.com>
To: Lee Jones <lee@...nel.org>
Cc: linux@...blig.org, arnd@...db.de, mchehab@...nel.org,
	lgirdwood@...il.com, broonie@...nel.org, perex@...ex.cz,
	tiwai@...e.com, linux-media@...r.kernel.org,
	linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] Remove the wl1273 FM Radio

On Tue, Sep 02, 2025 at 11:32:49AM +0100, Lee Jones wrote:
> On Fri, 08 Aug 2025, Laurent Pinchart wrote:
> > On Wed, Jun 25, 2025 at 02:32:54PM +0100, linux@...blig.org wrote:
> > > From: "Dr. David Alan Gilbert" <linux@...blig.org>
> > > 
> > > I noticed that the wl1273 radio had an unused symbol, but then noticed
> > > it is on Arnd's unused driver list:
> > >   https://lore.kernel.org/lkml/a15bb180-401d-49ad-a212-0c81d613fbc8@app.fastmail.com/
> > > 
> > > So, delete it.
> > > The components seem pretty separable, except for Kconfig dependencies.
> > > 
> > > That lore URL is over 75 chars, which checkpatch warns about,
> > > suggestions welcome.
> > > 
> > > Dave
> > > 
> > > Dr. David Alan Gilbert (4):
> > >   media: radio-wl1273: Remove
> > >   ASoC: wl1273: Remove
> > >   mfd: wl1273-core: Remove
> > >   mfd: wl1273-core: Remove the header
> > 
> > Mark, Lee, how would you like this to be merged ? I have a large patch
> > series targetting v6.18 that depends on 1/4, and I would like to merge
> > it in the media tree as soon as possible after -rc1 gets released.
> > Patches 1/4, 2/4 and 3/4 are independent of each other, but patch 4/4
> > depends on the first three. Can we merge 1/4 in the media tree and
> > provide a stable branch right on top of -rc1 ?
> 
> I'm also set-up pretty well to provide this.  Happy either way.
> 
> If you decide to take it:
> 
>   Acked-by: Lee Jones <lee@...nel.org>

Patch 1/4 has been queued in the media tree and should be in linux-next
as commit 103b0cfc9ab6. It is based straight on v6.17-rc1. Patch 2/4 is
also in linux-next, but is based on other ALSA patches. The simplest
course of action would be for you to merge 3/4 for v6.18, and 4/4 for
v6.19.

-- 
Regards,

Laurent Pinchart