All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@iki.fi>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, hverkuil@xs4all.nl,
	niklas.soderlund@ragnatech.se, laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH 0/9] Rework V4L2 fwnode parsing; add defaults and avoid iteration
Date: Fri, 5 Apr 2019 14:16:27 +0300	[thread overview]
Message-ID: <20190405111627.atbgsefad4gktlpp@valkosipuli.retiisi.org.uk> (raw)
In-Reply-To: <20190405094127.18975-1-sakari.ailus@linux.intel.com>

On Fri, Apr 05, 2019 at 12:41:17PM +0300, Sakari Ailus wrote:
> - Add another patch to change fwnode refcounting for
>   v4l2_async_notifier_add_fwnode_subdev
> 
> - Add a patch to fix OF node refcounting and use / put order for
>   davinci-vpif

If you wondered why does adding two patches to an 8-patch set makes a
9-patch set, the explanation is that another patch got dropped: "[RFC 3/8]
v4l2-fwnode: Use v4l2_async_notifier_add_fwnode_remote_subdev". The
parse_endpoint() may use information from async sub-device filled by the
same function.

-- 
Sakari Ailus

  parent reply	other threads:[~2019-04-05 11:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-05  9:41 [PATCH 0/9] Rework V4L2 fwnode parsing; add defaults and avoid iteration Sakari Ailus
2019-04-05  9:41 ` [PATCH 1/9] davinci-vpif: Don't dereference endpoint after putting it, fix refcounting Sakari Ailus
2019-04-05  9:41 ` [PATCH 1/9] davinci-vpif: Fix endpoint refcounting Sakari Ailus
2019-04-05 11:30   ` Ian Arkver
2019-04-05 11:34     ` Sakari Ailus
2019-04-05  9:41 ` [PATCH 2/9] v4l2-async: Use endpoint node, not device node, for fwnode match Sakari Ailus
2019-06-13  0:52   ` Niklas Söderlund
2019-04-05  9:41 ` [PATCH 3/9] v4l2-async: Get fwnode reference when putting it to the notifier's list Sakari Ailus
2019-04-05  9:41 ` [PATCH 4/9] v4l2-async: Add v4l2_async_notifier_add_fwnode_remote_subdev Sakari Ailus
2019-04-05  9:41 ` [PATCH 5/9] omap3isp: Rework OF endpoint parsing Sakari Ailus
2019-04-05  9:41 ` [PATCH 6/9] v4l2-async: Safely clean up an uninitialised notifier Sakari Ailus
2019-04-05  9:41 ` [PATCH 7/9] ipu3-cio2: Clean up notifier's subdev list if parsing endpoints fails Sakari Ailus
2019-04-05  9:41 ` [PATCH 8/9] ipu3-cio2: Proceed with notifier init even if there are no subdevs Sakari Ailus
2019-04-05  9:41 ` [PATCH 9/9] ipu3-cio2: Parse information from firmware without using callbacks Sakari Ailus
2019-04-05 11:16 ` Sakari Ailus [this message]
2019-04-12 15:33 ` [PATCH 0/9] Rework V4L2 fwnode parsing; add defaults and avoid iteration Jacopo Mondi
2019-04-12 20:27   ` Sakari Ailus

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=20190405111627.atbgsefad4gktlpp@valkosipuli.retiisi.org.uk \
    --to=sakari.ailus@iki.fi \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=niklas.soderlund@ragnatech.se \
    --cc=sakari.ailus@linux.intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.