From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oliver Neukum Date: Thu, 07 Dec 2017 09:17:11 +0000 Subject: Re: USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buffer() Message-Id: <1512638231.17062.5.camel@suse.com> List-Id: References: <97b0eeb8-834e-61ca-01dd-afbbf18697db@users.sourceforge.net> In-Reply-To: <97b0eeb8-834e-61ca-01dd-afbbf18697db@users.sourceforge.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Greg Kroah-Hartman , Geert Uytterhoeven Cc: Dmitry Fleytman , Daniel Drake , Eugene Korenevsky , Johan Hovold , Mathias Nyman , Peter Chen , Dan Carpenter , Joe Perches , =?ISO-8859-1?Q?G=FCnter_R=F6ck?= , Alan Stern , SF Markus Elfring , "kernel-janitors@vger.kernel.org" , LKML , USB list Am Donnerstag, den 07.12.2017, 09:56 +0100 schrieb Greg Kroah-Hartman: > On Thu, Dec 07, 2017 at 09:45:38AM +0100, Geert Uytterhoeven wrote: > > > > A few comments (this is in response to a patch from Markus, so there have > > to be lots of questions and uncertainties ;-) > > Note, because of the patch author, I'm not applying it no matter what, > so this discussion is really going nowhere. We really need to come to a consensus on that question. If those additional messages really are redundant, we could save memory deleting them. Or alternatively, if they are not and we need to know which device is hit, we should centralize that reporting and tell the VM subsystem not the dump a stack trace. Regards Oliver