From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] v4l: omap4iss: Replace outdated OMAP4 control pad API with syscon
Date: Sun, 12 Apr 2015 22:04:20 +0200 [thread overview]
Message-ID: <3942354.hKemp4fIKP@wuerfel> (raw)
In-Reply-To: <1428841693-15109-1-git-send-email-laurent.pinchart@ideasonboard.com>
On Sunday 12 April 2015 15:28:13 Laurent Pinchart wrote:
>
> Hi Arnd,
>
> This patch doesn't depend nor conflict with the OMAP4 ISS patches scheduled to
> be merged in v4.1. If Mauro is fine with that, and if it makes your life
> easier, it could get merged through the arm-soc tree. Please let me know what
> you prefer.
I think it's fine to merge it through the media/staging tree as normal.
I'm not as worried about bisection problems in staging drivers as elsewhere.
Thanks a lot for addressing this properly!
Arnd
prev parent reply other threads:[~2015-04-12 20:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 20:20 [PATCH] [media] omap4iss: avoid broken OMAP4 dependency Arnd Bergmann
2015-04-12 12:22 ` Laurent Pinchart
2015-04-12 12:28 ` [PATCH] v4l: omap4iss: Replace outdated OMAP4 control pad API with syscon Laurent Pinchart
2015-04-12 14:31 ` Sakari Ailus
2015-04-12 14:48 ` Laurent Pinchart
2015-04-12 20:04 ` Arnd Bergmann [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=3942354.hKemp4fIKP@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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).