From: Pavel Machek <pavel@ucw.cz>
To: Sebastian Reichel <sre@kernel.org>
Cc: sakari.ailus@iki.fi, pali.rohar@gmail.com,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
laurent.pinchart@ideasonboard.com, mchehab@kernel.org,
ivo.g.dimitrov.75@gmail.com
Subject: Re: [RFC 06/13] v4l2-async: per notifier locking
Date: Wed, 15 Feb 2017 11:58:56 +0100 [thread overview]
Message-ID: <20170215105856.GD29330@amd> (raw)
In-Reply-To: <20170214160720.xamqwoqo7rnb2nxi@earth>
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
Hi!
> > From: Sebastian Reichel <sre@kernel.org>
> >
> > Without this, camera support breaks boot on N900.
>
> That's kind of vague. I just checked my original patch and it looks
> like I did not bother to write a proper patch description. I suggest
> to make this
>
> "Fix v4l2-async locking, so that v4l2_async_notifiers can be used
> recursively. This is important for sensors, that are only reachable
> by the image signal processor through some intermediate device."
>
> You should probably move move this patch directly before the
> video-bus-switch patch, since its a preparation for it.
>
> Also this is missing my SoB:
>
> Signed-off-by: Sebastian Reichel <sre@kernel.org>
Thanks, done.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-02-15 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 13:39 [RFC 06/13] v4l2-async: per notifier locking Pavel Machek
2017-02-14 16:07 ` Sebastian Reichel
2017-02-15 10:58 ` Pavel Machek [this message]
2017-02-14 21:57 ` 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=20170215105856.GD29330@amd \
--to=pavel@ucw.cz \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=pali.rohar@gmail.com \
--cc=sakari.ailus@iki.fi \
--cc=sre@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