From: Shawn Guo <shawn.guo@freescale.com>
To: Stefan Agner <stefan@agner.ch>
Cc: <viresh.linux@gmail.com>, <shiraz.hashim@st.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <linux@arm.linux.org.uk>,
<linux-kernel@vger.kernel.org>, <ijc+devicetree@hellion.org.uk>,
Marek Vasut <marex@denx.de>
Subject: Re: [PATCH] ARM: dts: stmpe-ts: fix wrong bindings
Date: Wed, 2 Apr 2014 17:15:01 +0800 [thread overview]
Message-ID: <20140402091459.GB10283@dragon> (raw)
In-Reply-To: <2acd964e18e59b35996d042a3dd6e99b@agner.ch>
On Wed, Apr 02, 2014 at 09:48:58AM +0200, Stefan Agner wrote:
> Am 2013-12-09 21:32, schrieb Marek Vasut:
> > On Monday, December 09, 2013 at 09:15:11 PM, Stefan Agner wrote:
> >> Fix bindings for STMPE touchscreen device to match the documented
> >> bindings and the actual bindings used by the driver.
> >>
> >> Signed-off-by: Stefan Agner <stefan@agner.ch>
> >> ---
> >> I don't have any of these hardware, but the error is obvious. The device
> >> probably works anyway since the device/driver will use default values.
> >
> > Full agreement here.
> >
> > Reviewed-by: Marek Vasut <marex@denx.de>
> >
> > btw. I plan to rework the STMPE TS as it doesn't work nicely on my device at
> > all. I am seriously lacking time, but I will try! ;-)
> >
> > Best regards,
> > Marek Vasut
>
> Hi Shawn,
>
> Just noticed that I forgot to add you when sending this patch. I guess
> this should go through your tree...
You should probably resend the patch against the latest kernel, and with
imx change in a separate patch.
Shawn
prev parent reply other threads:[~2014-04-02 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 20:15 [PATCH] ARM: dts: stmpe-ts: fix wrong bindings Stefan Agner
2013-12-09 20:32 ` Marek Vasut
2014-04-02 7:48 ` Stefan Agner
2014-04-02 9:15 ` Shawn Guo [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=20140402091459.GB10283@dragon \
--to=shawn.guo@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marex@denx.de \
--cc=shiraz.hashim@st.com \
--cc=stefan@agner.ch \
--cc=viresh.linux@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