public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Arve Hj?nnev?g <arve@android.com>
Cc: Brian Swetland <swetland@google.com>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: HTC: touchscreen driver
Date: Tue, 21 Jul 2009 12:11:04 +0200	[thread overview]
Message-ID: <20090721101103.GD4133@elf.ucw.cz> (raw)
In-Reply-To: <d6200be20907192043w3f1aa2abvd0125163e6f5519c@mail.gmail.com>

On Sun 2009-07-19 20:43:10, Arve Hj?nnev?g wrote:
> On Sun, Jul 19, 2009 at 2:23 PM, Pavel Machek<pavel@ucw.cz> wrote:
> >
> >> > Applying small patch on top of cleaned up driver should be better than
> >> > carrying whole driver itself, right?
> >>
> >> Perhaps, but the only problem I encountered with this driver so far
> >> was when calling disable_irq from the interrupt handler stopped
> >> working on non-smp systems in 2.6.30 (which is another patch you
> >> should probably apply first).
> >
> > How do I get that patch? git pull on msm-2.6.29 tree?
> 
> No it is in the android-msm-2.6.30-rc2-test branch at
> git://android.git.kernel.org/kernel/experimental.git (commit
> 9f89902daf7a3c6fdd6b0c7494f3cc82d5e09217).

Could you inline the patch? I tried to pull it off the web interface,
but it did not work for some reason.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2009-07-21 10:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090710084323.GA6522@elf.ucw.cz>
     [not found] ` <a55d774e0907100155m25366994pe9ec5d0f5f868818@mail.gmail.com>
     [not found]   ` <20090710103243.GB7789@elf.ucw.cz>
     [not found]     ` <a55d774e0907100431j3fdc4671i6b185019594367fa@mail.gmail.com>
     [not found]       ` <20090713202302.GC2569@elf.ucw.cz>
2009-07-13 20:57         ` HTC: touchscreen driver Pavel Machek
2009-07-13 22:07           ` Pavel Machek
2009-07-14  1:29             ` Arve Hjønnevåg
2009-07-14  1:44               ` Joe Perches
2009-07-14  9:46                 ` Pavel Machek
2009-07-15 19:05                 ` Frank Rowand
2009-07-14  9:23               ` Pavel Machek
2009-07-14  9:46               ` Pavel Machek
2009-07-14 22:07                 ` Arve Hjønnevåg
2009-07-14 22:16                   ` Pavel Machek
2009-07-14 22:45                     ` Arve Hjønnevåg
2009-07-15  6:21                       ` Trilok Soni
2009-07-15  6:48                         ` Arve Hjønnevåg
2009-07-19 21:23                       ` Pavel Machek
2009-07-20  3:43                         ` Arve Hjønnevåg
2009-07-20 10:47                           ` Pavel Machek
2009-07-21 10:11                           ` Pavel Machek [this message]
2009-07-22  1:12                             ` Arve Hjønnevåg
2009-07-23 21:25                               ` Pavel Machek
2009-07-24  0:11                                 ` Arve Hjønnevåg
2009-07-27 23:14                                   ` Pavel Machek
2009-07-27 23:38                                     ` Arve Hjønnevåg
2009-07-14 10:02               ` Pavel Machek
2009-07-14  1:48             ` Daniel Walker
2009-07-14  6:47               ` Trilok Soni
2009-07-14  0:17           ` Brian Swetland
2009-07-14  9:47             ` Pavel Machek

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=20090721101103.GD4133@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=arve@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swetland@google.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