All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan De Luyck <lkml-gY0FE6dpLprYtjvyW6yDsg@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	Alexander Bruder <anib-IUH8PdohV+QGVwEePk/RpQ@public.gmane.org>
Subject: Re: [2.6.6] Synaptics driver is 'jumpy' -- FIXED
Date: Tue, 18 May 2004 12:49:41 +0200	[thread overview]
Message-ID: <200405181249.41787.lkml@kcore.org> (raw)
In-Reply-To: <1084821553.12352.358.camel-D2Zvc0uNKG8@public.gmane.org>

On Monday 17 May 2004 21:19, Len Brown wrote:
> On Mon, 2004-05-17 at 03:04, Jan De Luyck wrote:
> 2.6.6 dmesg:
>
> ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 11 12) *10
> ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 12
>
> Detected ipw2100 PCI device at 0000:02:04.0, dev: eth1, mem:
> 0xD0206000-0xD0206FFF -> e19e8000, irq: 12
>
> You need this patch:
> http://bugme.osdl.org/show_bug.cgi?id=2665

Thanks Len, this does the trick. 

Jan

-- 
His life was formal; his actions seemed ruled with a ruler.


-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click

WARNING: multiple messages have this Message-ID (diff)
From: Jan De Luyck <lkml@kcore.org>
To: Len Brown <len.brown@intel.com>
Cc: linux-kernel@vger.kernel.org,
	ACPI Developers <acpi-devel@lists.sourceforge.net>,
	Alexander Bruder <anib@uni-paderborn.de>
Subject: Re: [2.6.6] Synaptics driver is 'jumpy' -- FIXED
Date: Tue, 18 May 2004 12:49:41 +0200	[thread overview]
Message-ID: <200405181249.41787.lkml@kcore.org> (raw)
In-Reply-To: <1084821553.12352.358.camel@dhcppc4>

On Monday 17 May 2004 21:19, Len Brown wrote:
> On Mon, 2004-05-17 at 03:04, Jan De Luyck wrote:
> 2.6.6 dmesg:
>
> ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 11 12) *10
> ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 12
>
> Detected ipw2100 PCI device at 0000:02:04.0, dev: eth1, mem:
> 0xD0206000-0xD0206FFF -> e19e8000, irq: 12
>
> You need this patch:
> http://bugme.osdl.org/show_bug.cgi?id=2665

Thanks Len, this does the trick. 

Jan

-- 
His life was formal; his actions seemed ruled with a ruler.

  parent reply	other threads:[~2004-05-18 10:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A6974D8E5F98D511BB910002A50A6647615FBC01@hdsmsx403.hd.intel.com>
     [not found] ` <A6974D8E5F98D511BB910002A50A6647615FBC01-N2PTB0HCzHJviC08c4yzC1DQ4js95KgL@public.gmane.org>
2004-05-17 19:19   ` Re: [2.6.6] Synaptics driver is 'jumpy' Len Brown
2004-05-17 19:19     ` [ACPI] " Len Brown
     [not found]     ` <1084821553.12352.358.camel-D2Zvc0uNKG8@public.gmane.org>
2004-05-18 10:49       ` Jan De Luyck [this message]
2004-05-18 10:49         ` [2.6.6] Synaptics driver is 'jumpy' -- FIXED Jan De Luyck

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=200405181249.41787.lkml@kcore.org \
    --to=lkml-gy0fe6dplprytjvyw6ydsg@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=anib-IUH8PdohV+QGVwEePk/RpQ@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.