From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Magnus Damm <magnus.damm@gmail.com>,
Sakari Ailus <sakari.ailus@iki.fi>,
Prabhakar Lad <prabhakar.lad@ti.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: [PATCH] V4L2: add documentation for V4L2 clock helpers and asynchronous probing
Date: Mon, 24 Jun 2013 12:45:21 +0200 [thread overview]
Message-ID: <1734874.uLI0ndNzZS@avalon> (raw)
In-Reply-To: <Pine.LNX.4.64.1306241051060.19735@axis700.grange>
Hi Guennadi,
On Monday 24 June 2013 10:53:35 Guennadi Liakhovetski wrote:
> On Mon, 17 Jun 2013, Laurent Pinchart wrote:
>
> [snip]
>
> > > +drivers.
> > > +
> > > +Bridge drivers in turn have to register a notifier object with an array
> > > +of subdevice descriptors, that the bridge device needs for its
> > > +operation. This
> >
> > s/descriptors,/descriptors/
> >
> > > +is performed using the v4l2_async_notifier_register() call. To
> > > +unregister the notifier the driver has to call
> > > +v4l2_async_notifier_unregister(). The
> > > +former of the two functions takes two arguments: a pointer to struct
> > > +v4l2_device and a pointer to struct v4l2_async_notifier. The latter
> > > +contains a pointer to an array of pointers to subdevice descriptors of
> > > +type struct v4l2_async_subdev type.
> >
> > Isn't it the other way around ?
>
> I don't think I see anything above, that needs to be swapped. What exactly
> do you mean?
My bad. I got confused by "the latter" (which should be "the later" ;-)) and
thought it was referring to the later of the two functions, given that the
previous sentence starts with "the former of the two functions".
Maybe s/The format of the two functions/The first function/ and s/The
latter/The second structure/ ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-06-24 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 6:04 [PATCH] V4L2: add documentation for V4L2 clock helpers and asynchronous probing Guennadi Liakhovetski
2013-06-17 15:30 ` Prabhakar Lad
2013-06-17 19:54 ` Laurent Pinchart
2013-06-24 8:53 ` Guennadi Liakhovetski
2013-06-24 10:45 ` Laurent Pinchart [this message]
2013-06-21 18:25 ` Hans Verkuil
2013-06-21 20:27 ` Laurent Pinchart
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=1734874.uLI0ndNzZS@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=g.liakhovetski@gmx.de \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.lad@ti.com \
--cc=s.hauer@pengutronix.de \
--cc=s.nawrocki@samsung.com \
--cc=sakari.ailus@iki.fi \
/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