From: Mauro Carvalho Chehab <mchehab+huawei@kernel•org>
To: Mark Brown <broonie@kernel•org>
Cc: Sakari Ailus <sakari.ailus@linux•intel.com>,
Andy Shevchenko <andriy.shevchenko@intel•com>,
hansg@kernel•org, linux-media@vger•kernel.org,
mchehab@kernel•org,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: AtomISP tree for Linux Next
Date: Fri, 22 May 2026 20:23:36 +0200 [thread overview]
Message-ID: <20260522202336.216559c0@foz.lan> (raw)
In-Reply-To: <62b17869-008e-431b-a450-1b2e95111734@sirena.org.uk>
On Fri, 22 May 2026 13:10:00 +0100
Mark Brown <broonie@kernel•org> wrote:
> On Fri, May 22, 2026 at 09:59:53AM +0300, Sakari Ailus wrote:
>
> > I guess I could push patches to the atomisp branch after running them
> > through Media CI. But I'm not sure it's really worth it: the long backlog
> > of patches is now largely gone and the same fixes or cleanups can be only
> > merged once anyway. So would you expect the flow to still continue at a
> > similar level? There's a limit to which degree this driver can be improved
> > with such cleanups.
>
> FWIW so long as they don't cause conflicts all the time the marginal
> cost of including a tree is effectively nothing.
Sakari,
Patches committed at media-committers will appear at -next once they
reach media-pending (which, except if there are any sync issues, it
happens in a question of minutes). Just remind that we don't merge
patches for -next after -rc6 (except fixes, in which case you need
to warn me about that).
If nothing have changed, linux-next also has a similar policy of not
wanting patches that won't be merged for the next Kernel cycle,
which means that media patches after -rc6 would also wait for the
next -rc1 to be merged on a branch that goes to linux-next.
So, personally, I don't see any value on linux-next picking directly
from your atomisp tree, but that's up to you to decide.
Thanks,
Mauro
next prev parent reply other threads:[~2026-05-22 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 14:17 AtomISP tree for Linux Next Andy Shevchenko
2026-04-23 14:40 ` Mark Brown
2026-04-24 8:07 ` Andy Shevchenko
2026-05-22 6:59 ` Sakari Ailus
2026-05-22 12:10 ` Mark Brown
2026-05-22 18:23 ` Mauro Carvalho Chehab [this message]
2026-05-22 23:16 ` Mark Brown
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=20260522202336.216559c0@foz.lan \
--to=mchehab+huawei@kernel$(echo .)org \
--cc=andriy.shevchenko@intel$(echo .)com \
--cc=broonie@kernel$(echo .)org \
--cc=hansg@kernel$(echo .)org \
--cc=linux-media@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mchehab@kernel$(echo .)org \
--cc=sakari.ailus@linux$(echo .)intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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