From: "Zephaniah E. Hull" <warp@babylon.d2dc.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.2-rc2-mm1
Date: Fri, 30 Jan 2004 06:18:05 -0500 [thread overview]
Message-ID: <20040130111805.GC2505@babylon.d2dc.net> (raw)
In-Reply-To: <20040130110205.GA1583@ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 1464 bytes --]
On Fri, Jan 30, 2004 at 12:02:05PM +0100, Vojtech Pavlik wrote:
> On Fri, Jan 30, 2004 at 05:48:29AM -0500, Zephaniah E. Hull wrote:
> > On Tue, Jan 27, 2004 at 11:34:02PM -0800, Andrew Morton wrote:
> > >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.2-rc2/2.6.2-rc2-mm1/
> > >
> > > - From now on, -mm kernels will contain the latest contents of:
> > >
> > > Vojtech's tree: input.patch
> >
> > This one seems to have a rather problematic patch, which I can't find
> > any explanation for.
>
> There is another revision of the same mouse from A4Tech (owned by
> Jaroslav Kysela), that reports itself as Cypress and has the buttons a
> bit differently.
>
> If it indeed collides with your mouse, then we need somehow to specify
> which button carries the wheel information in the quirk list.
Ugh, that is not fun, it does indeed conflict.
How about HID_QUIRK_2WHEEL_MOUSE_HACK_EXTRA and
HID_QUIRK_2WHEEL_MOUSE_HACK_BACK as quirk names?
--
1024D/E65A7801 Zephaniah E. Hull <warp@babylon.d2dc.net>
92ED 94E4 B1E6 3624 226D 5727 4453 008B E65A 7801
CCs of replies from mailing lists are requested.
I could imagine that there might be some GPL project out there that
_deserves_ getting sued(*) and it has nothing to do with Linux.
Linus
(*) "GNU Emacs, the defendent, did inefariously conspire to play
towers-of-hanoy, while under the guise of a harmless editor".
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-30 11:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 7:34 2.6.2-rc2-mm1 Andrew Morton
2004-01-28 7:55 ` 2.6.2-rc2-mm1 Mike Fedyk
2004-01-28 8:18 ` ALSA noise (was: Re: 2.6.2-rc2-mm1) Joshua Kwan
2004-01-28 9:41 ` 2.6.2-rc2-mm1 Christoph Hellwig
2004-01-28 19:38 ` 2.6.2-rc2-mm1 David S. Miller
2004-01-28 12:08 ` 2.6.2-rc2-mm1 Ramon Rey Vicente
2004-01-28 12:13 ` 2.6.2-rc2-mm1 (Breakage?) David Martínez Moreno
2004-01-28 12:25 ` Alistair John Strachan
2004-01-28 13:33 ` Fix sleep_on abuse in XFS, Was: " Christoph Hellwig
2004-01-28 14:28 ` David Woodhouse
2004-01-28 15:02 ` Christoph Hellwig
2004-01-29 6:20 ` Nathan Scott
2004-01-29 23:37 ` Alexander Hoogerhuis
2004-01-28 12:17 ` 2.6.2-rc2-mm1 Nikita Danilov
2004-01-28 13:08 ` 2.6.2-rc2-mm1 Stian Jordet
2004-01-28 15:32 ` 2.6.2-rc2-mm1 Randy.Dunlap
2004-01-28 21:25 ` 2.6.2-rc2-mm1 Andrew Morton
2004-01-28 17:02 ` [BUG] [2.6.2-rc2-mm1] Badness in try_to_wake_up at kernel/sched.c:722 (was Re: 2.6.2-rc2-mm1) Ramon Rey Vicente
2004-01-28 19:55 ` 2.6.2-rc2-mm1 Torrey Hoffman
2004-01-29 16:15 ` 2.6.2-rc2-mm1 Zephaniah E. Hull
2004-01-30 10:48 ` 2.6.2-rc2-mm1 Zephaniah E. Hull
2004-01-30 11:02 ` 2.6.2-rc2-mm1 Vojtech Pavlik
2004-01-30 11:18 ` Zephaniah E. Hull [this message]
2004-01-30 11:20 ` 2.6.2-rc2-mm1 Vojtech Pavlik
2004-01-30 12:41 ` 2.6.2-rc2-mm1 Zephaniah E. Hull
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=20040130111805.GC2505@babylon.d2dc.net \
--to=warp@babylon.d2dc.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vojtech@suse.cz \
/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