[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y2fpRNxez+odikgL@sashalap>
Date: Sun, 6 Nov 2022 12:05:08 -0500
From: Sasha Levin <sashal@...nel.org>
To: Hans de Goede <hdegoede@...hat.com>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Andy Shevchenko <andy.shevchenko@...il.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
gregkh@...uxfoundation.org, linux-media@...r.kernel.org,
linux-staging@...ts.linux.dev
Subject: Re: [PATCH AUTOSEL 6.0 15/34] media: atomisp-ov2680: Fix
ov2680_set_fmt()
On Tue, Nov 01, 2022 at 02:27:53PM +0100, Hans de Goede wrote:
>Hi Sasha,
>
>I have no specific objections against the backporting of this
>and other atomisp related patches.
>
>But in general the atomisp driver is not yet in a state where
>it is ready to be used by normal users. Progress is being made
>but atm I don't really expect normal users to have it enabled /
>in active use.
>
>As such I'm also not sure if there is much value in backporting
>atomisp changes to the stable series.
>
>I don't know if you have a way to opt out certain drivers /
>file-paths from stable series backporting, but if you do
>you may want to consider opting out everything under:
>
>drivers/staging/media/atomisp/
>
>As said above I don't think doing the backports offers
>much (if any) value to end users and I assume it does take
>you some time, so opting this path out might be better.
>
>Also given the fragile state of atomisp support atm
>it is hard to say for me if partially backporting some of
>the changes won't break the driver.
I'll blacklist drivers/staging/media/atomisp/, thank you!
--
Thanks,
Sasha
Powered by blists - more mailing lists