linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Parag Warudkar" <parag.lkml@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-input@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: 2.6.28-rc9: USB Mouse unhappy
Date: Sun, 21 Dec 2008 01:26:00 -0500	[thread overview]
Message-ID: <f7848160812202226w1f930c86vfd17a2b0163bfc56@mail.gmail.com> (raw)
In-Reply-To: <20081220221253.e09b1b1f.akpm@linux-foundation.org>

On Sun, Dec 21, 2008 at 1:12 AM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> You're sure that 2.6.28-rc8 was OK?

Nope - not sure about 28-rc8. I meant to say some previous 28-rc's
that I tested worked fine - can't recall which ones. it is likely I
missed testing .28-rc8.

>
> 2.6.28-rc9 had only a small number of changes.  Nothing I can see in
> input or HID.  A few USB changes, but pretty specific ones -
> unusual_devs entries and such.
>
> Maybe your mouse has died?  Did you retest with an older kernel?
>
I did - rebooting into 2.6.27 (original distro kernel) makes it work again.

Thanks

Parag

  reply	other threads:[~2008-12-21  6:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f7848160812201911k7988221asd095ce873fd8105f@mail.gmail.com>
     [not found] ` <f7848160812201911k7988221asd095ce873fd8105f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-12-21  6:12   ` 2.6.28-rc9: USB Mouse unhappy Andrew Morton
2008-12-21  6:26     ` Parag Warudkar [this message]
2008-12-21 10:56       ` Anssi Hannula
2008-12-21 15:17         ` Parag Warudkar
2008-12-21 17:30           ` Jiri Kosina
     [not found]             ` <alpine.LRH.1.10.0812211824350.11630-1ReQVI26iDCaZKY3DrU6dA@public.gmane.org>
2008-12-21 18:39               ` Jiri Kosina
     [not found]                 ` <alpine.LRH.1.10.0812211939170.11630-1ReQVI26iDCaZKY3DrU6dA@public.gmane.org>
2009-01-09 23:11                   ` Rafael J. Wysocki
2009-01-09 23:18                     ` Parag Warudkar
     [not found]                     ` <200901100011.35332.rjw-KKrjLPT3xs0@public.gmane.org>
2009-01-09 23:19                       ` Jiri Kosina
2009-01-10  0:19                         ` Rafael J. Wysocki
2008-12-21 19:49               ` [PATCH] USBHID: Make Boot Protocol drivers depend on EMBEDDED Parag Warudkar
2008-12-21 21:48                 ` Jiri Kosina
     [not found]                   ` <alpine.LNX.1.10.0812212247090.26265-YCXOAqNspd+N3ZZ/Hiejyg@public.gmane.org>
2008-12-21 22:02                     ` Andrew Morton
2008-12-21 22:03                       ` Jiri Kosina
     [not found]                         ` <alpine.LNX.1.10.0812212302400.26265-YCXOAqNspd+N3ZZ/Hiejyg@public.gmane.org>
2008-12-21 22:12                           ` Parag Warudkar
2008-12-21 22:17                             ` Anssi Hannula
2008-12-21 22:23                               ` Parag Warudkar
2008-12-21 22:44                                 ` Jiri Kosina
2008-12-21 23:55                                   ` Parag Warudkar
2008-12-22 21:52                 ` Jiri Kosina

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=f7848160812202226w1f930c86vfd17a2b0163bfc56@mail.gmail.com \
    --to=parag.lkml@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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;
as well as URLs for NNTP newsgroup(s).