From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, akinobu.mita@gmail.com,
hverkuil@xs4all.nl, bparrot@ti.com
Subject: Re: [PATCH 3/4] pxa-camera: Match with device node, not the port node
Date: Wed, 21 Aug 2019 09:26:59 +0200 [thread overview]
Message-ID: <87d0gzj7wc.fsf@belgarion.home> (raw)
In-Reply-To: <20190305135602.24199-4-sakari.ailus@linux.intel.com> (Sakari Ailus's message of "Tue, 5 Mar 2019 15:56:01 +0200")
Sakari Ailus <sakari.ailus@linux.intel.com> writes:
> V4L2 fwnode matching right now still works based on device nodes, not port
> nodes. Fix this.
Mmmh why does it need a fix, and what's wrong on device node matching ? This
commit message is a bit too brief for me to understand why a fix is needed.
Moreover, does it have an impact on
Documentation/devicetree/bindings/media/pxa-camera.txt ?
Cheers.
--
Robert
next prev parent reply other threads:[~2019-08-21 7:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 13:55 [PATCH 0/4] V4L2 fwnode framework and driver fixes Sakari Ailus
2019-03-05 13:55 ` [PATCH 1/4] v4l2-fwnode: Defaults may not override endpoint configuration in firmware Sakari Ailus
2019-03-05 13:56 ` [PATCH 2/4] v4l2-fwnode: The first default data lane is 0 on C-PHY Sakari Ailus
2019-03-05 13:56 ` [PATCH 3/4] pxa-camera: Match with device node, not the port node Sakari Ailus
2019-08-21 7:26 ` Robert Jarzmik [this message]
2019-08-21 8:24 ` Sakari Ailus
2019-03-05 13:56 ` [PATCH 4/4] ti-vpe: Parse local endpoint for properties, not the remote one Sakari Ailus
2019-03-05 14:02 ` [PATCH v1.1 " Sakari Ailus
2019-03-05 14:34 ` Benoit Parrot
2019-03-05 16:32 ` Sakari Ailus
2019-03-05 17:38 ` Benoit Parrot
2019-03-05 20:48 ` Sakari Ailus
2019-03-07 15:34 ` Benoit Parrot
2019-03-07 15:55 ` Sakari Ailus
2019-03-07 21:25 ` [PATCH " kbuild test robot
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=87d0gzj7wc.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=akinobu.mita@gmail.com \
--cc=bparrot@ti.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--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 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).