* AtomISP tree for Linux Next
@ 2026-04-23 14:17 Andy Shevchenko
2026-04-23 14:40 ` Mark Brown
0 siblings, 1 reply; 7+ messages in thread
From: Andy Shevchenko @ 2026-04-23 14:17 UTC (permalink / raw)
To: Mark Brown, sakari.ailus, hansg
Cc: linux-media, mchehab, Linux Next Mailing List
Hi, Mark!
I think I will express the thought hanging in the air that AtomISP driver needs
to be exposed in Linux Next tree. Currently it's being stored on linuxtv.org
servers [1] which I think is not often appear in the Linux Next. So, for now
can you add that tree to Linux next
Also note, that one of the reasons behind this is a flow of patches against
the driver that basically repeat each other or unapplicable due to newcomers
have a hard time to realise that they need to be based on a niche tree.
[1]: https://git.linuxtv.org/sailus/media_tree.git/log/?h=atomisp
Tree: git://linuxtv.org/sailus/media_tree.git
https://git.linuxtv.org/sailus/media_tree.git
Branch: atomisp
--
With Best Regards,
Andy Shevchenko
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: AtomISP tree for Linux Next
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
0 siblings, 1 reply; 7+ messages in thread
From: Mark Brown @ 2026-04-23 14:40 UTC (permalink / raw)
To: Andy Shevchenko
Cc: sakari.ailus, hansg, linux-media, mchehab,
Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
On Thu, Apr 23, 2026 at 05:17:30PM +0300, Andy Shevchenko wrote:
> I think I will express the thought hanging in the air that AtomISP driver needs
> to be exposed in Linux Next tree. Currently it's being stored on linuxtv.org
> servers [1] which I think is not often appear in the Linux Next. So, for now
> can you add that tree to Linux next
> Also note, that one of the reasons behind this is a flow of patches against
> the driver that basically repeat each other or unapplicable due to newcomers
> have a hard time to realise that they need to be based on a niche tree.
> [1]: https://git.linuxtv.org/sailus/media_tree.git/log/?h=atomisp
> Tree: git://linuxtv.org/sailus/media_tree.git
> https://git.linuxtv.org/sailus/media_tree.git
> Branch: atomisp
That'd be totally fine of course if the people working on the tree are
happy with that - it looks like it's Sakari?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: AtomISP tree for Linux Next
2026-04-23 14:40 ` Mark Brown
@ 2026-04-24 8:07 ` Andy Shevchenko
2026-05-22 6:59 ` Sakari Ailus
0 siblings, 1 reply; 7+ messages in thread
From: Andy Shevchenko @ 2026-04-24 8:07 UTC (permalink / raw)
To: Mark Brown
Cc: sakari.ailus, hansg, linux-media, mchehab,
Linux Next Mailing List
On Thu, Apr 23, 2026 at 03:40:36PM +0100, Mark Brown wrote:
> On Thu, Apr 23, 2026 at 05:17:30PM +0300, Andy Shevchenko wrote:
>
> > I think I will express the thought hanging in the air that AtomISP driver needs
> > to be exposed in Linux Next tree. Currently it's being stored on linuxtv.org
> > servers [1] which I think is not often appear in the Linux Next. So, for now
> > can you add that tree to Linux next
>
> > Also note, that one of the reasons behind this is a flow of patches against
> > the driver that basically repeat each other or unapplicable due to newcomers
> > have a hard time to realise that they need to be based on a niche tree.
>
> > [1]: https://git.linuxtv.org/sailus/media_tree.git/log/?h=atomisp
>
> > Tree: git://linuxtv.org/sailus/media_tree.git
> > https://git.linuxtv.org/sailus/media_tree.git
> > Branch: atomisp
>
> That'd be totally fine of course if the people working on the tree are
> happy with that - it looks like it's Sakari?
He is the maintainer, I'm a reviewer. Sakari, can you confirm the inclusion of
the tree into Linux Next daily integration/builds?
--
With Best Regards,
Andy Shevchenko
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: AtomISP tree for Linux Next
2026-04-24 8:07 ` Andy Shevchenko
@ 2026-05-22 6:59 ` Sakari Ailus
2026-05-22 12:10 ` Mark Brown
0 siblings, 1 reply; 7+ messages in thread
From: Sakari Ailus @ 2026-05-22 6:59 UTC (permalink / raw)
To: Andy Shevchenko
Cc: Mark Brown, hansg, linux-media, mchehab, Linux Next Mailing List
Hi Andy, Mark,
On Fri, Apr 24, 2026 at 11:07:32AM +0300, Andy Shevchenko wrote:
> On Thu, Apr 23, 2026 at 03:40:36PM +0100, Mark Brown wrote:
> > On Thu, Apr 23, 2026 at 05:17:30PM +0300, Andy Shevchenko wrote:
> >
> > > I think I will express the thought hanging in the air that AtomISP driver needs
> > > to be exposed in Linux Next tree. Currently it's being stored on linuxtv.org
> > > servers [1] which I think is not often appear in the Linux Next. So, for now
> > > can you add that tree to Linux next
> >
> > > Also note, that one of the reasons behind this is a flow of patches against
> > > the driver that basically repeat each other or unapplicable due to newcomers
> > > have a hard time to realise that they need to be based on a niche tree.
> >
> > > [1]: https://git.linuxtv.org/sailus/media_tree.git/log/?h=atomisp
> >
> > > Tree: git://linuxtv.org/sailus/media_tree.git
> > > https://git.linuxtv.org/sailus/media_tree.git
> > > Branch: atomisp
> >
> > That'd be totally fine of course if the people working on the tree are
> > happy with that - it looks like it's Sakari?
>
> He is the maintainer, I'm a reviewer. Sakari, can you confirm the inclusion of
> the tree into Linux Next daily integration/builds?
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.
--
Regards,
Sakari Ailus
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: AtomISP tree for Linux Next
2026-05-22 6:59 ` Sakari Ailus
@ 2026-05-22 12:10 ` Mark Brown
2026-05-22 18:23 ` Mauro Carvalho Chehab
0 siblings, 1 reply; 7+ messages in thread
From: Mark Brown @ 2026-05-22 12:10 UTC (permalink / raw)
To: Sakari Ailus
Cc: Andy Shevchenko, hansg, linux-media, mchehab,
Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: AtomISP tree for Linux Next
2026-05-22 12:10 ` Mark Brown
@ 2026-05-22 18:23 ` Mauro Carvalho Chehab
2026-05-22 23:16 ` Mark Brown
0 siblings, 1 reply; 7+ messages in thread
From: Mauro Carvalho Chehab @ 2026-05-22 18:23 UTC (permalink / raw)
To: Mark Brown
Cc: Sakari Ailus, Andy Shevchenko, hansg, linux-media, mchehab,
Linux Next Mailing List
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: AtomISP tree for Linux Next
2026-05-22 18:23 ` Mauro Carvalho Chehab
@ 2026-05-22 23:16 ` Mark Brown
0 siblings, 0 replies; 7+ messages in thread
From: Mark Brown @ 2026-05-22 23:16 UTC (permalink / raw)
To: Mauro Carvalho Chehab
Cc: Sakari Ailus, Andy Shevchenko, hansg, linux-media, mchehab,
Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 361 bytes --]
On Fri, May 22, 2026 at 08:23:36PM +0200, Mauro Carvalho Chehab wrote:
> 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.
That's correct, yes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2026-05-22 23:16 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2026-05-22 23:16 ` Mark Brown
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox