linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/8] Use gpio_request_one() in SH Mobile board code
Date: Fri, 11 Jan 2013 09:46:15 +0000	[thread overview]
Message-ID: <1939733.2hrOhEyhvK@avalon> (raw)
In-Reply-To: <1357847279-7765-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>

Hi Simon,

On Friday 11 January 2013 16:08:25 Simon Horman wrote:
> On Thu, Jan 10, 2013 at 08:47:51PM +0100, Laurent Pinchart wrote:
> > Hello,
> > 
> > Here's a small patch set that converts gpio_request() + gpio_direction_*()
> > calls into gpio_request_one() in all SH Mobile board files.
> > 
> > The patches are based on top of "[PATCH v2 00/29] SH pinctrl and pinmux
> > implementation". I will rebase my next version of the pinctrl DT patches
> > on
> > top of them.
> 
> I may be confused but I believe that I have already merged the pinctl DT
> patches in their form "[PATCH v2 0/8] SH pinctrl DT support".
> 
> Could you either rebase this series on top of the next branch in the reneas
> tree or; Indicate that I should drop "[PATCH v2 0/8] SH pinctrl DT support".
> 
> I have a slight preference for the first option.

The DT series hasn't been acked, and I'm still unsure about the DT bindings, 
so I expect at least one more iteration of the patches. It should thus not be 
merged yet (I'm sorry for not having stated that explicitly when posting the 
patch set). This is why I've based this series on top of the pinctrl + pinmux 
implementation, as it doesn't depend on the DT patches (I would of course like 
to get acks before merging it).

-- 
Regards,

Laurent Pinchart


      parent reply	other threads:[~2013-01-11  9:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 19:47 [PATCH 0/8] Use gpio_request_one() in SH Mobile board code Laurent Pinchart
2013-01-11  7:08 ` Simon Horman
2013-01-11  9:46 ` 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=1939733.2hrOhEyhvK@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).