From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-m68k@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Atari input patches
Date: Mon, 9 May 2011 09:10:17 +0200 [thread overview]
Message-ID: <BANLkTi=CMAJrkAsKP4_QEaDVSw8Cz_RJfQ@mail.gmail.com> (raw)
In-Reply-To: <20110509060048.GA27577@core.coreip.homeip.net>
Hi Dmitry,
On Mon, May 9, 2011 at 08:00, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> On Sun, May 08, 2011 at 11:17:24AM +0200, Geert Uytterhoeven wrote:
>> Here are 3 patches to fix keyboard and mouse on Atari, after conversion to
>> the "new" (several years old) input framework.
>>
>> [1/3] input/atari: Use the correct mouse interrupt hook
>> [2/3] input/atari: Fix atarimouse init
>> [3/3] input/atari: Fix mouse movement and button mapping
>>
>> Will you take them for 2.6.40, or can I get them in through my m68k tree?
>
> I can either take them or you can push them. I do not really have a
> preference. There is nothing in my tree that would conflict with these
> as far as I know.
In that case I'll push them myself. Thx again!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2011-05-09 7:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 9:17 Geert Uytterhoeven
2011-05-08 9:17 ` [PATCH 1/3] input/atari: Use the correct mouse interrupt hook Geert Uytterhoeven
2011-05-08 9:17 ` [PATCH 2/3] input/atari: Fix atarimouse init Geert Uytterhoeven
2011-05-08 9:17 ` [PATCH 3/3] input/atari: Fix mouse movement and button mapping Geert Uytterhoeven
2011-05-09 6:00 ` [PATCH 0/3] Atari input patches Dmitry Torokhov
2011-05-09 7:10 ` Geert Uytterhoeven [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='BANLkTi=CMAJrkAsKP4_QEaDVSw8Cz_RJfQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@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
all inboxes | Powered by JetHome®