From: Bastian Hecht <hechtb@gmail.com>
To: Simon Horman <horms@verge.net.au>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Linux-SH <linux-sh@vger.kernel.org>,
linux-input@vger.kernel.org,
Tony SIM <chinyeow.sim.xt@renesas.com>,
Magnus Damm <magnus.damm@gmail.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: [PATCH v2 2/2] ARM: shmobile: Armadillo800EVA: Move st1232 reset pin handling
Date: Tue, 9 Apr 2013 17:04:06 +0200 [thread overview]
Message-ID: <CABYn4swK4bVEYediYPdR3nQSTZ=YfUNpEDGGVOXWKYssQ3_z_w@mail.gmail.com> (raw)
In-Reply-To: <20130409150154.GB27787@verge.net.au>
2013/4/9 Simon Horman <horms@verge.net.au>:
> On Tue, Apr 09, 2013 at 11:16:18AM +0200, Bastian Hecht wrote:
>> 2013/4/9 Simon Horman <horms@verge.net.au>:
>> > On Tue, Apr 09, 2013 at 05:26:44PM +0900, Simon Horman wrote:
>> >> On Mon, Apr 08, 2013 at 04:17:22PM +0200, Laurent Pinchart wrote:
>> >> > Hi Bastian,
>> >> >
>> >> > Thanks for the patch.
>> >> >
>> >> > On Monday 08 April 2013 14:52:27 Bastian Hecht wrote:
>> >> > > We no longer need to set up the reset pin for the st1232 in the board
>> >> > > code, but can pass the GPIO number via the platform data to the driver.
>> >> > > This results in a cleaner grouping of the device setup.
>> >> > >
>> >> > > Signed-off-by: Bastian Hecht <hechtb+renesas@gmail.com>
>> >> >
>> >> > Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>> >>
>> >> Thanks.
>> >>
>> >> I have queued this up in the boards-armadillo800eva branch.
>> >>
>> >> There were some conflicts when I applied the code which
>> >> I fixed manually. Bastian, can you please check that the
>> >> following is correct? If it is not please send an incremental patch.
>> >
>> > I was trying to apply your patch to an old branch.
>> > It applies cleanly to the correct new branch :)
>>
>> Ah sweet, I was indeed a bit confused about going back to the INTC as
>> primary controller.
>
> After all that I had to drop the patch as it depends on patch 1/2.
> Lets sort out which tree that patch is going through.
> I have sent an email to try and sort that out.
Thanks Simon!
next prev parent reply other threads:[~2013-04-09 15:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 12:52 [PATCH v2 1/2] input: st1232: Add reset pin handling Bastian Hecht
2013-04-08 12:52 ` [PATCH v2 2/2] ARM: shmobile: Armadillo800EVA: Move st1232 " Bastian Hecht
2013-04-08 14:17 ` Laurent Pinchart
2013-04-09 8:26 ` Simon Horman
2013-04-09 9:11 ` Simon Horman
2013-04-09 9:16 ` Bastian Hecht
2013-04-09 11:55 ` Simon Horman
2013-04-09 15:01 ` Simon Horman
2013-04-09 15:04 ` Bastian Hecht [this message]
2013-04-08 14:17 ` [PATCH v2 1/2] input: st1232: Add " Laurent Pinchart
2013-04-09 8:28 ` Simon Horman
2013-04-09 9:23 ` Bastian Hecht
2013-04-09 15:01 ` Simon Horman
2013-04-10 6:51 ` Dmitry Torokhov
2013-04-10 7:25 ` Simon Horman
2013-04-10 6:51 ` Dmitry Torokhov
2013-04-10 9:11 ` Laurent Pinchart
2013-04-10 21:38 ` Bastian Hecht
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='CABYn4swK4bVEYediYPdR3nQSTZ=YfUNpEDGGVOXWKYssQ3_z_w@mail.gmail.com' \
--to=hechtb@gmail.com \
--cc=chinyeow.sim.xt@renesas.com \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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).