From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [0/4] Remove the wl1273 FM Radio
Date: Sat, 9 Aug 2025 00:23:59 +0000 [thread overview]
Message-ID: <aJaVH5eCDhLutPSn@gallifrey> (raw)
In-Reply-To: <20250808160123.GE23187@pendragon.ideasonboard.com>
* Laurent Pinchart (laurent.pinchart@ideasonboard.com) wrote:
> On Fri, Aug 08, 2025 at 02:09:56PM +0000, Dr. David Alan Gilbert wrote:
> > * Laurent Pinchart (laurent.pinchart@ideasonboard.com) wrote:
> > > On Thu, Jun 26, 2025 at 12:50:18PM +0000, Dr. David Alan Gilbert wrote:
> > > > * Patchwork Integration (patchwork@media-ci.org) wrote:
> > > > > Dear Dr. David Alan Gilbert:
> > > > >
> > > > > Thanks for your patches! Unfortunately the Media CI robot detected some
> > > > > issues:
> > > > >
> > > > > # Test checkpatch:./0001-media-radio-wl1273-Remove.patch checkpatch
> > > > > WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
> > > > > #7:
> > > > > https://lore.kernel.org/lkml/a15bb180-401d-49ad-a212-0c81d613fbc8@app.fastmail.com/
> > > > >
> > > > > WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
> > > > > #61:
> > > > > deleted file mode 100644
> > > > >
> > > > > total: 0 errors, 2 warnings, 0 checks, 30 lines checked
> > > >
> > > > I did check that, couldn't find any appropriate MAINTAINERS entry anyway
> > > >
> > > > > # Test checkpatch:./0002-ASoC-wl1273-Remove.patch checkpatch
> > > > > WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
> > > > > #7:
> > > > > https://lore.kernel.org/lkml/a15bb180-401d-49ad-a212-0c81d613fbc8@app.fastmail.com/
> > > >
> > > > Yep, said that in my cover letter; suggestions on how to refer to that URL
> > > > in a better way are welcome.
> > >
> > > You can ignore those two warnings.
> >
> > Thanks for confirming that.
> > Could you (or some other -media maintainer) pick 1/4 for linux-media please;
> > Generally I think Lee tends only to pick the mfd specific bit up, so I need
> > to get the specifics in through the other trees.
>
> We can take patch 1/4 in the media tree, but merging the different
> pieces in an uncoordinated fashion will result in breakages in
> linux-next :-/
It should be safe to go in order; so you taking patch 1/4 should move
things forward.
Dave
> I think the simplest option would be to create a branch on top of v6.16
> (or v6.17-rc1) with the 4 patches applied, and merge it in the media,
> mfd and sound trees. That would require Lee to drop patches 3/4 and 4/4
> that he already applied to the mfd tree though.
>
> > > > > WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
> > > > > #71:
> > > > > deleted file mode 100644
> > > > >
> > > > > total: 0 errors, 2 warnings, 0 checks, 36 lines checked
> > > > >
> > > > > # Test checkpatch:./0003-mfd-wl1273-core-Remove.patch checkpatch
> > > > > WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
> > > > > #8:
> > > > > https://lore.kernel.org/lkml/a15bb180-401d-49ad-a212-0c81d613fbc8@app.fastmail.com/
> > > > >
> > > > > WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
> > > > > #55:
> > > > > deleted file mode 100644
> > > > >
> > > > > total: 0 errors, 2 warnings, 0 checks, 23 lines checked
> > > > >
> > > > > # Test checkpatch:./0004-mfd-wl1273-core-Remove-the-header.patch checkpatch
> > > > > WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
> > > > > #7:
> > > > > https://lore.kernel.org/lkml/a15bb180-401d-49ad-a212-0c81d613fbc8@app.fastmail.com/
> > > > >
> > > > > WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
> > > > > #35:
> > > > > deleted file mode 100644
> > > > >
> > > > > total: 0 errors, 2 warnings, 0 checks, 7 lines checked
> > > > >
> > > > >
> > > > >
> > > > > Please fix your series, and upload a new version. If you have a patchwork
> > > > > account, do not forget to mark the current series as Superseded.
> > > > >
> > > > > For more details, check the full report at:
> > > > > https://linux-media.pages.freedesktop.org/-/users/patchwork/-/jobs/79088843/artifacts/report.htm .
> > > > >
> > > > >
> > > > >
> > > > > Best regards, and Happy Hacking!
> > > > > Media CI robot on behalf of the linux-media community.
> > > > >
> > > > > ---
> > > > > Check the latest rules for contributing your patches at:
> > > > > https://docs.kernel.org/driver-api/media/maintainer-entry-profile.html
> > > > >
> > > > > If you believe that the CI is wrong, kindly open an issue at
> > > > > https://gitlab.freedesktop.org/linux-media/media-ci/-/issues or reply-all
> > > > > to this message.
> > > > >
>
> --
> Regards,
>
> Laurent Pinchart
--
-----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-08-09 0:24 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 [this message]
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
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=aJaVH5eCDhLutPSn@gallifrey \
--to=linux@treblig.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.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