From: "Arnd Bergmann" <arnd@arndb.de>
To: "Hans Verkuil" <hverkuil-cisco@xs4all.nl>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>
Cc: "Arnd Bergmann" <arnd@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
"Mauro Carvalho Chehab" <mchehab@kernel.org>
Subject: Re: [PATCH] media: v4l: marvell: select CONFIG_V4L2_ASYNC where needed
Date: Wed, 14 Feb 2024 11:58:07 +0100 [thread overview]
Message-ID: <7ec182c6-bd52-4433-bf06-dbc71f186184@app.fastmail.com> (raw)
In-Reply-To: <6067898e-eaac-4266-b4a3-388db9a918fa@xs4all.nl>
On Wed, Feb 14, 2024, at 11:54, Hans Verkuil wrote:
> On 14/02/2024 11:48, Arnd Bergmann wrote:
>
>> It was definitely working before ff3cc65cadb5 ("media: v4l: async,
>> fwnode: Improve module organisation") in linux-5.13, but it's not
>> clear if that is the culprit. It's probably safe to backport
>> to v5.15 and higher.
>
>
> If it has been broken for so long, then should we bother with v6.8?
>
> I'm not saying we should, I just like to get your opinion on this.
I don't have a strong opinion either way, there is very little
risk and very little benefit in backporting.
If we apply it to 6.8 at all, I think it should also be in
v5.15+ LTS and vice versa, but only queuing it for 6.9 is
fine with me, too.
Arnd
next prev parent reply other threads:[~2024-02-14 10:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 9:55 Arnd Bergmann
2024-02-14 10:24 ` Hans Verkuil
2024-02-14 10:33 ` Arnd Bergmann
2024-02-14 10:33 ` Sakari Ailus
2024-02-14 10:48 ` Arnd Bergmann
2024-02-14 10:54 ` Hans Verkuil
2024-02-14 10:58 ` Arnd Bergmann [this message]
2024-02-14 12:42 ` Hans Verkuil
2024-02-14 15:03 ` Sakari Ailus
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=7ec182c6-bd52-4433-bf06-dbc71f186184@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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
all inboxes | Powered by JetHome®