From: Greg KH <greg@kroah.com>
To: Alan Cox <alan@linux.intel.com>
Cc: linux-input@vger.kernel.org, dmitry.torokhov@gmail.com
Subject: Re: [PATCH 2/2] intel_mid_touch: Resync upstream with the development tree
Date: Tue, 31 Aug 2010 15:17:48 -0700 [thread overview]
Message-ID: <20100831221748.GD14846@kroah.com> (raw)
In-Reply-To: <20100825142217.2831.18768.stgit@localhost.localdomain>
On Wed, Aug 25, 2010 at 03:22:22PM +0100, Alan Cox wrote:
> This merges bits from the two diverging trees including code by Andy Ross
> and Arjan van de Ven
But it doesn't apply to my staging tree, odd.
Care to respin it against linux-next? Is there something in linux-next
from Dmitry for this driver that might be getting me confused here?
thanks,
greg k-h
next prev parent reply other threads:[~2010-08-31 22:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 14:22 [PATCH 1/2] fix channel allocation in the touch screen driver Alan Cox
2010-08-25 14:22 ` [PATCH 2/2] intel_mid_touch: Resync upstream with the development tree Alan Cox
2010-08-31 22:17 ` Greg KH [this message]
2010-09-01 6:23 ` Dmitry Torokhov
2010-09-01 15:04 ` Greg KH
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=20100831221748.GD14846@kroah.com \
--to=greg@kroah.com \
--cc=alan@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@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).