From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: dts: imx28-evk: Enable touchscreen support
Date: Tue, 28 May 2013 06:56:27 +0200 [thread overview]
Message-ID: <201305280656.27472.marex@denx.de> (raw)
In-Reply-To: <20130528014348.GA19608@S2101-09.ap.freescale.net>
Dear Shawn Guo,
> On Mon, May 27, 2013 at 09:52:21PM -0300, Fabio Estevam wrote:
> > Hi Shawn,
> >
> > On Mon, May 13, 2013 at 11:31 PM, Shawn Guo <shawn.guo@linaro.org> wrote:
> > > Have you tested it against v3.10-rc1? The issue is still there in my
> > > testing.
> >
> > I am not able to see the issue on 3.10-rc2.
>
> My imx/dt branch is currently basing on v3.10-rc1, and I do not care if
> it works on v3.10-rc2. I have tested this patch enough on different
> bases, and I'm not going to test it again and again to find a base which
> happens to work. I do not feel comfortable to merge this patch if it
> only works on particular base. Who knows if it will break again with
> another random patches merged in. There is some issue, and we need to
> find the root cause of it instead of ignoring it by finding some random
> base which hides it.
>
> > What are the exact steps to trigger the problem? Do you see it
> > consistently?
>
> Before I answer your questions, can I ask if you have tried to reproduce
> it on v3.10-rc1?
What is the problem you observe?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-05-28 4:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 15:36 [PATCH 1/3] ARM: dts: imx28-evk: Enable touchscreen support Fabio Estevam
2013-02-08 15:36 ` [PATCH 2/3] ARM: dts: imx28-apx4devkit: " Fabio Estevam
2013-02-08 15:47 ` Lauri Hintsala
2013-02-08 15:36 ` [PATCH 3/3] ARM: mxs_defconfig: Build CONFIG_INPUT_EVDEV as built-in Fabio Estevam
2013-02-17 7:54 ` [PATCH 1/3] ARM: dts: imx28-evk: Enable touchscreen support Shawn Guo
2013-02-17 10:31 ` Marek Vasut
2013-02-17 12:04 ` Shawn Guo
2013-02-18 14:43 ` Marek Vasut
2013-03-04 3:17 ` Shawn Guo
2013-03-05 14:07 ` Fabio Estevam
2013-03-05 14:21 ` Shawn Guo
2013-03-05 14:21 ` Fabio Estevam
2013-03-05 14:25 ` Fabio Estevam
2013-03-05 16:11 ` Fabio Estevam
2013-03-22 18:07 ` Fabio Estevam
2013-03-23 13:56 ` Shawn Guo
2013-03-23 18:09 ` Fabio Estevam
2013-03-24 14:18 ` Shawn Guo
2013-05-13 11:48 ` Fabio Estevam
2013-05-14 2:31 ` Shawn Guo
2013-05-14 3:30 ` Marek Vasut
2013-05-28 0:52 ` Fabio Estevam
2013-05-28 1:43 ` Shawn Guo
2013-05-28 4:56 ` Marek Vasut [this message]
2013-05-28 6:27 ` Shawn Guo
2013-05-28 18:29 ` Marek Vasut
2013-05-29 2:00 ` Shawn Guo
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=201305280656.27472.marex@denx.de \
--to=marex@denx.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).