public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel•com>
To: Mark Brown <broonie@kernel•org>,
	sakari.ailus@linux•intel.com, hansg@kernel•org
Cc: linux-media@vger•kernel.org, mchehab@kernel•org,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: AtomISP tree for Linux Next
Date: Thu, 23 Apr 2026 17:17:30 +0300	[thread overview]
Message-ID: <aeop-rkoHOgF2OgQ@ashevche-desk.local> (raw)

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



             reply	other threads:[~2026-04-23 14:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23 14:17 Andy Shevchenko [this message]
2026-04-23 14:40 ` AtomISP tree for Linux Next 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

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=aeop-rkoHOgF2OgQ@ashevche-desk.local \
    --to=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