[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200924154026.GA9761@carbon.lan>
Date: Thu, 24 Sep 2020 18:40:26 +0300
From: Petko Manolov <petkan@...leusys.com>
To: Oliver Neukum <oneukum@...e.com>
Cc: Himadri Pandya <himadrispandya@...il.com>, davem@...emloft.net,
kuba@...nel.org, pankaj.laxminarayan.bharadiya@...el.com,
keescook@...omium.org, yuehaibing@...wei.com, ogiannou@...il.com,
linux-usb@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-kernel-mentees@...ts.linuxfoundation.org,
gregkh@...uxfoundation.org
Subject: Re: [PATCH 3/4] net: usb: rtl8150: use usb_control_msg_recv() and
usb_control_msg_send()
On 20-09-24 13:09:05, Oliver Neukum wrote:
> Am Mittwoch, den 23.09.2020, 17:48 +0300 schrieb Petko Manolov:
>
> > One possible fix is to add yet another argument to usb_control_msg_recv(),
> > which would be the GFP_XYZ flag to pass on to kmemdup(). Up to Greg, of
> > course.
>
> submitted. The problem is those usages that are very hard to trace. I'd
> dislike to just slab GFP_NOIO on them for no obvious reason.
Do you mean you submitted a patch for usb_control_msg_recv() (because i don't
see it on linux-netdev) or i'm reading this all wrong?
Petko
Powered by blists - more mailing lists