From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Li Wu <willy.woo@gmail.com>
Cc: balbi@ti.com, Li Wu <li.wu@st.com>,
Henrik Rydberg <rydberg@euromail.se>,
Andrew Morton <akpm@linux-foundation.org>,
Joe Perches <joe@perches.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"David S. Miller" <davem@davemloft.net>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Shawn Landden <shawnlandden@gmail.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Jianchun <jcbian@pixcir.com.cn>,
David Dajun Chen <dchen@diasemi.com>,
Ashish Jangam <ashish.jangam@kpitcummins.com>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
device-drivers-devel@blackfin.uclinux.org
Subject: Re: [PATCH 1/1] Input: STMicroelectronics multi touch capacitive touchscreen ftk
Date: Mon, 3 Dec 2012 17:44:43 -0800 [thread overview]
Message-ID: <20121204014442.GA23039@core.coreip.homeip.net> (raw)
In-Reply-To: <CAEdoeCM94F3RT8J4w8i3S6GJ5Upy1CBCatnuwiFB_7ZzB0Cn6Q@mail.gmail.com>
Hi Li,
On Tue, Dec 04, 2012 at 08:32:05AM +0800, Li Wu wrote:
> Thanks Felipe for the nice comments.
>
> I have consolidated most of your comments to a new version, but I am not
> sure how should I send it out.
>
> I am using git send-email from shell command, then shall I just send out
> the patch v2? Or do I need send both v1 and v2?
Use "git rebase" to squash the 2 commit together and then send it out as
a single patch.
Thanks.
--
Dmitry
prev parent reply other threads:[~2012-12-04 1:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 14:18 [PATCH 1/1] Input: STMicroelectronics multi touch capacitive touchscreen ftk Li Wu
2012-11-30 15:04 ` Felipe Balbi
2012-11-30 15:40 ` Joe Perches
[not found] ` <CAEdoeCM94F3RT8J4w8i3S6GJ5Upy1CBCatnuwiFB_7ZzB0Cn6Q@mail.gmail.com>
2012-12-04 1:44 ` Dmitry Torokhov [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=20121204014442.GA23039@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ashish.jangam@kpitcummins.com \
--cc=balbi@ti.com \
--cc=davem@davemloft.net \
--cc=dchen@diasemi.com \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=gregkh@linuxfoundation.org \
--cc=jcbian@pixcir.com.cn \
--cc=joe@perches.com \
--cc=li.wu@st.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=rydberg@euromail.se \
--cc=shawnlandden@gmail.com \
--cc=viresh.kumar@linaro.org \
--cc=willy.woo@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).