From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Lee Jones <lee@kernel.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Mark Brown <broonie@kernel.org>,
arnd@arndb.de, mchehab@kernel.org, lgirdwood@gmail.com,
perex@perex.cz, tiwai@suse.com, linux-media@vger.kernel.org,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] Remove the wl1273 FM Radio
Date: Thu, 2 Oct 2025 20:32:15 +0000 [thread overview]
Message-ID: <aN7hT_59V6KcOxTe@gallifrey> (raw)
In-Reply-To: <20250903072301.GZ2163762@google.com>
* Lee Jones (lee@kernel.org) wrote:
> On Tue, 02 Sep 2025, Dr. David Alan Gilbert wrote:
>
> > * Laurent Pinchart (laurent.pinchart@ideasonboard.com) wrote:
> > > On Tue, Sep 02, 2025 at 12:47:39PM +0100, Mark Brown wrote:
> > > > On Tue, Sep 02, 2025 at 01:35:27PM +0200, Laurent Pinchart wrote:
> > > >
> > > > > 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.
> > > >
> > > > Or given that it's a driver removal we could just get a rebase of the
> > > > series against the meda tree applied? The conflicts with ASoC should be
> > > > trivial to resolve.
> > >
> > > I don't mind either way. I know Linus doesn't like having the same patch
> > > merged with different commit IDs, but I don't know how strict the rule
> > > is, especially when git should be able to resolve the conflict
> > > transparently.
> >
> > I still think the easiest thing is to leave 1/4 and 2/4 as you currently
> > have them; and let Lee take 3/4 and 4/4 next time around.
>
> It's more disjointed than I like. But it's okay. Remind me later.
Hi Lee,
1 and 2 of this series just got merged into Linus' tree.
Thanks all!
3 and 4 can go in at your convenience.
Dave
> --
> Lee Jones [李琼斯]
>
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2025-10-02 20:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 13:32 [PATCH 0/4] Remove the wl1273 FM Radio linux
2025-06-25 13:32 ` [PATCH 1/4] media: radio-wl1273: Remove linux
2025-08-08 15:52 ` Laurent Pinchart
2025-06-25 13:32 ` [PATCH 2/4] ASoC: wl1273: Remove linux
2025-06-25 14:04 ` Mark Brown
2025-08-14 13:59 ` Dr. David Alan Gilbert
2025-06-25 13:32 ` [PATCH 3/4] mfd: wl1273-core: Remove linux
2025-06-25 13:32 ` [PATCH 4/4] mfd: wl1273-core: Remove the header linux
2025-06-25 14:00 ` [PATCH 0/4] Remove the wl1273 FM Radio Arnd Bergmann
2025-07-01 13:27 ` (subset) " Lee Jones
2025-08-08 15:51 ` Laurent Pinchart
2025-08-08 16:01 ` Dr. David Alan Gilbert
2025-08-08 15:49 ` Laurent Pinchart
2025-09-02 10:32 ` Lee Jones
2025-09-02 10:35 ` Mark Brown
2025-09-02 11:35 ` Laurent Pinchart
2025-09-02 11:47 ` Mark Brown
2025-09-02 12:10 ` Laurent Pinchart
2025-09-02 17:49 ` Dr. David Alan Gilbert
2025-09-03 7:23 ` Lee Jones
2025-10-02 20:32 ` Dr. David Alan Gilbert [this message]
2025-08-10 4:31 ` [PATCH] checkpatch: Allow http links of any length in commit logs Joe Perches
2025-08-14 20:08 ` (subset) [PATCH 0/4] Remove the wl1273 FM Radio Mark Brown
2025-08-15 11:29 ` Dr. David Alan Gilbert
2025-10-09 15:08 ` Lee Jones
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=aN7hT_59V6KcOxTe@gallifrey \
--to=linux@treblig.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
/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