From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Mark Brown <broonie@kernel.org>
Cc: Lee Jones <lee@kernel.org>,
linux@treblig.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: Tue, 2 Sep 2025 14:10:15 +0200 [thread overview]
Message-ID: <20250902121015.GI13448@pendragon.ideasonboard.com> (raw)
In-Reply-To: <88042d72-b428-442e-ba3c-b15e587e12a7@sirena.org.uk>
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.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2025-09-02 12:10 UTC|newest]
Thread overview: 32+ 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
[not found] ` <685c08d5.050a0220.350bff.01b0@mx.google.com>
2025-06-26 12:50 ` [0/4] " Dr. David Alan Gilbert
2025-08-08 14:04 ` Laurent Pinchart
2025-08-08 14:09 ` Dr. David Alan Gilbert
2025-08-08 16:01 ` Laurent Pinchart
2025-08-09 0:23 ` Dr. David Alan Gilbert
2025-08-09 22:01 ` Laurent Pinchart
2025-08-14 13:57 ` Dr. David Alan Gilbert
2025-08-14 14:07 ` Laurent Pinchart
2025-07-01 13:27 ` (subset) [PATCH 0/4] " 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 [this message]
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
2025-08-14 20:08 ` (subset) " 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=20250902121015.GI13448@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--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=linux@treblig.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