From: Oliver Neukum <oliver@neukum.org>
To: Henk Martijn <h.h.martijn@gmail.com>
Cc: linux-input@vger.kernel.org, linux-usb@vger.kernel.org,
Greg KH <gregkh@suse.de>, Jiri Kosina <jkosina@suse.cz>
Subject: Re: [patch]fix usbhid using GFP_KERNEL in interrupt
Date: Mon, 21 Sep 2009 22:37:18 +0200 [thread overview]
Message-ID: <200909212237.19281.oliver@neukum.org> (raw)
In-Reply-To: <4AB7E331.8050209@gmail.com>
Am Montag, 21. September 2009 22:33:53 schrieb Henk Martijn:
> Oliver Neukum wrote:
> > hid:usbhid: fix wrong use of GFP_KERNEL
> >
> > hid_input_report() must be told it is called in interrupt context
> >
> > Signed-off-by: Oliver Neukum <oliver@neukum.org>
> >
> > Hi Jiri, Greg,
> >
> > this should go into the current tree and the stable tree.
>
> Stable? Interestingly I did not have any problems with 2.6.31......
OK, Greg, hold your fire. Jiri is this necessary in stable?
Regards
Oliver
next prev parent reply other threads:[~2009-09-21 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 20:25 [patch]fix usbhid using GFP_KERNEL in interrupt Oliver Neukum
2009-09-21 20:33 ` Henk Martijn
2009-09-21 20:37 ` Oliver Neukum [this message]
2009-09-21 21:42 ` 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=200909212237.19281.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=gregkh@suse.de \
--cc=h.h.martijn@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@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