public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>,
	mkrufky@m1k.net, frank.peters@comcast.net, vojtech@suse.cz
Subject: Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems
Date: Sat, 30 Jul 2005 00:57:36 -0500	[thread overview]
Message-ID: <200507300057.36921.dtor_core@ameritech.net> (raw)
In-Reply-To: <20050729213724.01c61c26.akpm@osdl.org>

On Friday 29 July 2005 23:37, Andrew Morton wrote:
> 
> The diff between 2.6.12-rc4-mm2 and 2.6.12-rc5-mm1 is enormous, but there
> aren't any significant input driver changes there:
> http://www.zip.com.au/~akpm/linux/patches/stuff/diffstat-2.6.12-rc4-mm2-2.6.12-rc5-mm1
> 

>From the original thread it seems that the usual suspects (input and
ACPI updates) were not causing the failure, at leat not directly:

> >>I applied bk-input.patch directly to 2.6.12-rc5, and it did NOT break it 
> >>this time.  Looks like either a different patch is the culprit, or the 
> >>combination of this patch and another.
> >>
> >>    
> >>
> >
> >Please try adding bk-acpi to the mix.
> >
> >  
> >
> Combination of both bk-input and bk-acpi applied to 2.6.12-rc5 still 
> doesn't break it.  What next?

Some other patch must be messing things up somehow...

-- 
Dmitry

  reply	other threads:[~2005-07-30  5:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24 15:34 Asus MB and 2.6.12 Problems Frank Peters
2005-06-24 16:10 ` isa0060/serio0 problems -WAS- " Michael Krufky
2005-06-24 16:59   ` Frank Peters
2005-06-24 17:12     ` Michael Krufky
     [not found]       ` <20050728222838.64517cc9.akpm@osdl.org>
2005-07-29  5:44         ` Michael Krufky
2005-07-29  5:54           ` Andrew Morton
2005-07-30  2:44             ` Zwane Mwaikambo
2005-07-30  3:48             ` Michael Krufky
2005-07-30  3:52               ` Michael Krufky
2005-07-30  4:18                 ` Michael Krufky
2005-07-30  4:37               ` Andrew Morton
2005-07-30  5:57                 ` Dmitry Torokhov [this message]
2005-07-30  6:34                 ` Frank Peters
2005-07-31 18:45                   ` Vojtech Pavlik
2005-07-31 19:24                     ` Frank Peters
2005-07-31 20:42                       ` Andrew Morton
2005-07-31 23:48                         ` Frank Peters
2005-07-29 18:33         ` Frank Peters
     [not found]           ` <20050804162812.29a3f2b2.akpm@osdl.org>
2005-08-05  3:09             ` Frank Peters
2005-08-05  3:20               ` Dmitry Torokhov
2005-08-05  3:54                 ` Andrew Morton
2005-08-05  4:07                   ` Dmitry Torokhov
2005-08-05 10:40                     ` Marc Ballarin
2005-08-05  4:07                   ` Michael Krufky
2005-08-05  6:43                     ` Vojtech Pavlik
2005-08-04 20:19       ` Andrew Morton
2005-06-27 11:39   ` Michael Krufky
     [not found] ` <1119633158.3180.5.camel@home-lap>
2005-06-24 18:07   ` Frank Peters
2005-06-26 19:47 ` Alexey Dobriyan
  -- strict thread matches above, loose matches on Subject: below --
2005-07-30  8:33 isa0060/serio0 problems -WAS- " Andrey Borzenkov

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=200507300057.36921.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=akpm@osdl.org \
    --cc=frank.peters@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkrufky@m1k.net \
    --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