[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZczWMRuSYABtDsVu@kekkonen.localdomain>
Date: Wed, 14 Feb 2024 15:03:13 +0000
From: Sakari Ailus <sakari.ailus@...ux.intel.com>
To: Hans Verkuil <hverkuil-cisco@...all.nl>
Cc: Arnd Bergmann <arnd@...db.de>, Arnd Bergmann <arnd@...nel.org>,
linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
Mauro Carvalho Chehab <mchehab@...nel.org>
Subject: Re: [PATCH] media: v4l: marvell: select CONFIG_V4L2_ASYNC where
needed
On Wed, Feb 14, 2024 at 01:42:55PM +0100, Hans Verkuil wrote:
> On 14/02/2024 11:58, Arnd Bergmann wrote:
> > 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.
>
> OK, I'll just take this patch as-is for v6.9. I'm preparing a PR
> anyway, so I'll include this patch.
>
> Thank you for the quick replies!
Feel free to add:
Acked-by: Sakari Ailus <sakari.ailus@...ux.intel.com>
--
Sakari Ailus
Powered by blists - more mailing lists