linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Ezequiel Garcia <ezequiel@collabora.com>
Cc: linux-media@vger.kernel.org, ezequiel.garcia@collabora.com
Subject: Re: [PATCH v3 1/1] v4l: async, fwnode: Improve module organisation
Date: Thu, 6 May 2021 09:28:16 +0300	[thread overview]
Message-ID: <20210506062816.GT3@paasikivi.fi.intel.com> (raw)
In-Reply-To: <0c0bf5d35c3098188dc594268e721f8133f38789.camel@collabora.com>

On Wed, May 05, 2021 at 07:12:30PM -0300, Ezequiel Garcia wrote:
> On Wed, 2021-05-05 at 00:06 +0300, Sakari Ailus wrote:
> > The V4L2 async framework is generally used with the V4L2 fwnode, which
> > also depends on the former. There are a few exceptions but they are
> > relatively few.
> > 
> > At the same time there is a vast number of systems that need videodev
> > module, but have no use for v4l2-async that's now part of videodev.
> > 
> > In order to improve, split the v4l2-async into its own module. Selecting
> > V4L2_FWNODE also selects V4L2_ASYNC.
> > 
> > This also moves the initialisation of the debufs entries for async subdevs
> > to loading of the v4l2-async module. The directory is named as
> > "v4l2-async".
> > 
> > Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> 
> Reviewed-by: Ezequiel Garcia <ezequiel@collabora.com>

Thanks, Ezequiel!

-- 
Sakari Ailus

      reply	other threads:[~2021-05-06  6:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04 21:06 [PATCH v3 1/1] v4l: async, fwnode: Improve module organisation Sakari Ailus
2021-05-05 22:12 ` Ezequiel Garcia
2021-05-06  6:28   ` Sakari Ailus [this message]

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=20210506062816.GT3@paasikivi.fi.intel.com \
    --to=sakari.ailus@linux.intel.com \
    --cc=ezequiel.garcia@collabora.com \
    --cc=ezequiel@collabora.com \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).