From: Greg KH <gregkh@linuxfoundation.org>
To: Hyeonggon Yoo <42.hyeyoo@gmail.com>
Cc: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
linux-usb@vger.kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: usbmouse: Avoid GFP_ATOMIC when GFP_KERNEL is possible
Date: Thu, 27 May 2021 18:54:07 +0200 [thread overview]
Message-ID: <YK/Or91JIpbpwWjL@kroah.com> (raw)
In-Reply-To: <20210527164517.GA143281@hyeyoo>
On Fri, May 28, 2021 at 01:45:17AM +0900, Hyeonggon Yoo wrote:
> On Mon, May 24, 2021 at 11:57:43PM +0900, Hyeonggon Yoo wrote:
> > probe in usb don't need to be atomic. So GFP_KERNEL can be used here,
> > instead of GFP_ATOMIC.
> >
> > Signed-off-by: Hyeonggon Yoo <42.hyeyoo@gmail.com>
> > ---
> > drivers/hid/usbhid/usbmouse.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/hid/usbhid/usbmouse.c b/drivers/hid/usbhid/usbmouse.c
> > index 073127e65ac1..c89332017d5d 100644
> > --- a/drivers/hid/usbhid/usbmouse.c
> > +++ b/drivers/hid/usbhid/usbmouse.c
> > @@ -130,7 +130,7 @@ static int usb_mouse_probe(struct usb_interface *intf, const struct usb_device_i
> > if (!mouse || !input_dev)
> > goto fail1;
> >
> > - mouse->data = usb_alloc_coherent(dev, 8, GFP_ATOMIC, &mouse->data_dma);
> > + mouse->data = usb_alloc_coherent(dev, 8, GFP_KERNEL, &mouse->data_dma);
> > if (!mouse->data)
> > goto fail1;
> >
> > --
> > 2.25.1
> >
>
> Hello for me it was simple and obvious patch.
> Is there something wrong about it?
It has been only 4 days. For a non-bugfix and for something that is
only a "cleanup" change, give it at least 2 weeks please.
Relax, there is no rush for stuff like this.
thanks,
greg k-h
next prev parent reply other threads:[~2021-05-27 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 14:57 [PATCH] HID: usbmouse: Avoid GFP_ATOMIC when GFP_KERNEL is possible Hyeonggon Yoo
2021-05-27 16:45 ` Hyeonggon Yoo
2021-05-27 16:54 ` Greg KH [this message]
2021-05-27 17:05 ` Hyeonggon Yoo
2021-05-27 17:11 ` Greg KH
2021-05-28 20:54 ` Hyeonggon Yoo
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=YK/Or91JIpbpwWjL@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=42.hyeyoo@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.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