All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: "USB list" <linux-usb@vger.kernel.org>,
	"Alan Stern" <stern@rowland.harvard.edu>,
	"Daniel Drake" <drake@endlessm.com>,
	"Dmitry Fleytman" <dmitry@daynix.com>,
	"Eugene Korenevsky" <ekorenevsky@gmail.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Günter Röck" <linux@roeck-us.net>,
	"Johan Hovold" <johan@kernel.org>,
	"Mathias Nyman" <mathias.nyman@linux.intel.com>,
	"Peter Chen" <peter.chen@nxp.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>
Subject: Re: USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buffer()
Date: Wed, 6 Dec 2017 21:20:05 +0100	[thread overview]
Message-ID: <CAMuHMdWdMWfYjSkMCd-B_DBBfLa3Aixprw4ziRA3ccVEo6TXAA@mail.gmail.com> (raw)
In-Reply-To: <97b0eeb8-834e-61ca-01dd-afbbf18697db@users.sourceforge.net>

Hi Markus,

On Wed, Dec 6, 2017 at 6:51 PM, SF Markus Elfring
<elfring@users.sourceforge.net> wrote:
>> The system will come to a grinding halt anyway if it can't allocate 24 or 40 bytes.
>
> Maybe.

Since you've been sending zillions of patches for this, perhaps the time
is ripe to actually try to trigger this, and see what happens?

>> Which is BTW more or less the amount of memory saved by killing
>> the useless (error) message.
>
> Would you dare to resend this update suggestion after such a view?

Of course. That was implied.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: "USB list" <linux-usb@vger.kernel.org>,
	"Alan Stern" <stern@rowland.harvard.edu>,
	"Daniel Drake" <drake@endlessm.com>,
	"Dmitry Fleytman" <dmitry@daynix.com>,
	"Eugene Korenevsky" <ekorenevsky@gmail.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Günter Röck" <linux@roeck-us.net>,
	"Johan Hovold" <johan@kernel.org>,
	"Mathias Nyman" <mathias.nyman@linux.intel.com>,
	"Peter Chen" <peter.chen@nxp.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>
Subject: Re: USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buffer()
Date: Wed, 06 Dec 2017 20:20:05 +0000	[thread overview]
Message-ID: <CAMuHMdWdMWfYjSkMCd-B_DBBfLa3Aixprw4ziRA3ccVEo6TXAA@mail.gmail.com> (raw)
In-Reply-To: <97b0eeb8-834e-61ca-01dd-afbbf18697db@users.sourceforge.net>

Hi Markus,

On Wed, Dec 6, 2017 at 6:51 PM, SF Markus Elfring
<elfring@users.sourceforge.net> wrote:
>> The system will come to a grinding halt anyway if it can't allocate 24 or 40 bytes.
>
> Maybe.

Since you've been sending zillions of patches for this, perhaps the time
is ripe to actually try to trigger this, and see what happens?

>> Which is BTW more or less the amount of memory saved by killing
>> the useless (error) message.
>
> Would you dare to resend this update suggestion after such a view?

Of course. That was implied.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: "USB list" <linux-usb@vger.kernel.org>,
	"Alan Stern" <stern@rowland.harvard.edu>,
	"Daniel Drake" <drake@endlessm.com>,
	"Dmitry Fleytman" <dmitry@daynix.com>,
	"Eugene Korenevsky" <ekorenevsky@gmail.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Günter Röck" <linux@roeck-us.net>,
	"Johan Hovold" <johan@kernel.org>,
	"Mathias Nyman" <mathias.nyman@linux.intel.com>,
	"Peter Chen" <peter.chen@nxp.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>
Subject: USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buffer()
Date: Wed, 6 Dec 2017 21:20:05 +0100	[thread overview]
Message-ID: <CAMuHMdWdMWfYjSkMCd-B_DBBfLa3Aixprw4ziRA3ccVEo6TXAA@mail.gmail.com> (raw)

Hi Markus,

On Wed, Dec 6, 2017 at 6:51 PM, SF Markus Elfring
<elfring@users.sourceforge.net> wrote:
>> The system will come to a grinding halt anyway if it can't allocate 24 or 40 bytes.
>
> Maybe.

Since you've been sending zillions of patches for this, perhaps the time
is ripe to actually try to trigger this, and see what happens?

>> Which is BTW more or less the amount of memory saved by killing
>> the useless (error) message.
>
> Would you dare to resend this update suggestion after such a view?

Of course. That was implied.

Gr{oetje,eeting}s,

                        Geert
---
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-12-06 20:20 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06 16:13 [PATCH] USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buffer() SF Markus Elfring
2017-12-06 16:13 ` SF Markus Elfring
2017-12-06 16:13 ` [PATCH] USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buffer( SF Markus Elfring
2017-12-06 16:45 ` [PATCH] USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buffer() Alan Stern
2017-12-06 16:45   ` Alan Stern
2017-12-06 16:45   ` [PATCH] USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buf Alan Stern
2017-12-06 16:57   ` [PATCH] USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buffer() Greg Kroah-Hartman
2017-12-06 16:57     ` Greg Kroah-Hartman
2017-12-06 16:57     ` [PATCH] USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buf Greg Kroah-Hartman
2017-12-06 17:27   ` [PATCH] USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buffer() Geert Uytterhoeven
2017-12-06 17:27     ` Geert Uytterhoeven
2017-12-06 17:27     ` [PATCH] USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buf Geert Uytterhoeven
2017-12-06 17:51     ` USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buffer() SF Markus Elfring
2017-12-06 17:51       ` SF Markus Elfring
2017-12-06 17:51       ` SF Markus Elfring
2017-12-06 20:20       ` Geert Uytterhoeven [this message]
2017-12-06 20:20         ` Geert Uytterhoeven
2017-12-06 20:20         ` Geert Uytterhoeven
2017-12-08 11:11         ` Dan Carpenter
2017-12-08 11:11           ` Dan Carpenter
2017-12-08 11:11           ` Dan Carpenter
2017-12-08 12:00           ` USB: hub: Checking communication difficulties SF Markus Elfring
2017-12-08 12:00             ` USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buffer() SF Markus Elfring
2017-12-08 12:00             ` USB: hub: Checking communication difficulties SF Markus Elfring
2017-12-06 20:05   ` [PATCH] USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buffer() Joe Perches
2017-12-06 20:05     ` Joe Perches
2017-12-06 20:05     ` [PATCH] USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buf Joe Perches
2017-12-06 21:18     ` [PATCH] USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buffer() Alan Stern
2017-12-06 21:18       ` Alan Stern
2017-12-06 21:18       ` [PATCH] USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buf Alan Stern
2017-12-06 21:33       ` USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buffer() SF Markus Elfring
2017-12-06 21:33         ` SF Markus Elfring
2017-12-06 21:33         ` SF Markus Elfring
2017-12-06 22:02         ` Alan Stern
2017-12-06 22:02           ` Alan Stern
2017-12-06 22:02           ` Alan Stern
2017-12-07  7:40           ` Geert Uytterhoeven
2017-12-07  7:40             ` Geert Uytterhoeven
2017-12-07  7:40             ` Geert Uytterhoeven
2017-12-07  8:35             ` Dan Carpenter
2017-12-07  8:35               ` Dan Carpenter
2017-12-07  8:35               ` Dan Carpenter
2017-12-07  8:45               ` Geert Uytterhoeven
2017-12-07  8:45                 ` Geert Uytterhoeven
2017-12-07  8:45                 ` Geert Uytterhoeven
2017-12-07  8:56                 ` Greg Kroah-Hartman
2017-12-07  8:56                   ` Greg Kroah-Hartman
2017-12-07  8:56                   ` Greg Kroah-Hartman
2017-12-07  9:17                   ` Oliver Neukum
2017-12-07  9:17                     ` Oliver Neukum
2017-12-07  9:17                     ` Oliver Neukum
2017-12-07  9:30                 ` Dan Carpenter
2017-12-07  9:30                   ` Dan Carpenter
2017-12-07  9:30                   ` Dan Carpenter
2017-12-07 15:12             ` Alan Stern
2017-12-07 15:12               ` Alan Stern
2017-12-07 15:12               ` Alan Stern
2017-12-07 16:20               ` Joe Perches
2017-12-07 16:20                 ` Joe Perches
2017-12-07 16:20                 ` Joe Perches
2017-12-07 20:51               ` Dan Carpenter
2017-12-07 20:51                 ` Dan Carpenter
2017-12-07 20:51                 ` Dan Carpenter
2017-12-07 21:26                 ` Alan Stern
2017-12-07 21:26                   ` Alan Stern
2017-12-07 21:26                   ` Alan Stern
2017-12-08  7:43                   ` Geert Uytterhoeven
2017-12-08  7:43                     ` Geert Uytterhoeven
2017-12-08  7:43                     ` Geert Uytterhoeven
2017-12-08 17:42                     ` Alan Stern
2017-12-08 17:42                       ` Alan Stern
2017-12-08 17:42                       ` Alan Stern
2017-12-07 13:38           ` SF Markus Elfring
2017-12-07 13:38             ` SF Markus Elfring
2017-12-07 13:38             ` SF Markus Elfring

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=CAMuHMdWdMWfYjSkMCd-B_DBBfLa3Aixprw4ziRA3ccVEo6TXAA@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=dmitry@daynix.com \
    --cc=drake@endlessm.com \
    --cc=ekorenevsky@gmail.com \
    --cc=elfring@users.sourceforge.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mathias.nyman@linux.intel.com \
    --cc=peter.chen@nxp.com \
    --cc=stern@rowland.harvard.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.