From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v3 00/81] SH pin control and GPIO rework
Date: Wed, 19 Dec 2012 21:24:10 +0000 [thread overview]
Message-ID: <1586031.1BSJIX9nKm@avalon> (raw)
In-Reply-To: <1355611915-25060-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
Hi Linus,
On Wednesday 19 December 2012 16:31:00 Linus Walleij wrote:
> On Sat, Dec 15, 2012 at 11:50 PM, Laurent Pinchart wrote:
> > I would like to push this set to v3.9 independently of the later rework
> > and OF-related sets. Linus and Simon, which tree would you like me to push
> > this through ?
>
> The pinctrl or sh tree obviously :-)
>
> Basically if you believe there will be colissions with other stuff in
> the sh tree it should go in through that tree. Obviously there is little
> risk of collissions in the pinctrl tree as this is a new driver.
I believe the risk of collisions in the SH and ARM trees are higher than in
the pinctrl tree, so it would probably better to push the patches through
Simon.
> You can add my Acked-by: to the entire patch set, since the result at
> the end is super-nice.
Thank you.
I'll push a public branch on top of v3.8-rc1 when it will be released, and
will send a pull request a couple of weeks later.
> I think there were review comments of mine that were not fixed yet,
> but I trust you to go through that and fix it up as time goes by.
They will be addressed by new patch series. This one is already pretty big, I
didn't want to delay it anymore.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2012-12-19 21:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-15 22:50 [PATCH v3 00/81] SH pin control and GPIO rework Laurent Pinchart
2012-12-18 2:06 ` Simon Horman
2012-12-19 15:31 ` Linus Walleij
2012-12-19 21:24 ` Laurent Pinchart [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=1586031.1BSJIX9nKm@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.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;
as well as URLs for NNTP newsgroup(s).