From: Oliver Neukum <oneukum@suse.com>
To: Kloetzke Jan <Jan.Kloetzke@preh.de>,
"davem@davemloft.net" <davem@davemloft.net>
Cc: "jan@kloetzke.net" <jan@kloetzke.net>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH v2] usbnet: fix kernel crash after disconnect
Date: Tue, 21 May 2019 13:42:24 +0200 [thread overview]
Message-ID: <1558438944.12672.13.camel@suse.com> (raw)
In-Reply-To: <1558433542.19453.33.camel@preh.de>
On Di, 2019-05-21 at 10:12 +0000, Kloetzke Jan wrote:
>
> Why not just take v1 of the patch?
>
> https://lore.kernel.org/netdev/20190417091849.7475-1-Jan.Kloetzke@preh.de/
>
> The original version was exactly the same, just without the WARN_ON().
> Or is it required to send a v3 in this case?
It will make things easier for Dave to pick up.
Regards
Oliver
next prev parent reply other threads:[~2019-05-21 11:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 9:19 [PATCH] usbnet: fix kernel crash after disconnect Kloetzke Jan
2019-04-17 9:19 ` Kloetzke Jan
2019-04-18 6:37 ` [PATCH] " Oliver Neukum
2019-04-18 6:37 ` Oliver Neukum
2019-04-18 8:02 ` [PATCH] " Kloetzke Jan
2019-04-18 8:02 ` Kloetzke Jan
2019-04-18 23:35 ` [PATCH] " David Miller
2019-04-18 23:35 ` David Miller
2019-04-19 7:17 ` [PATCH] " Jan Klötzke
2019-04-19 7:17 ` Jan Klötzke
2019-04-29 18:48 ` [PATCH] " Oliver Neukum
2019-04-29 18:48 ` Oliver Neukum
2019-04-30 14:08 ` [PATCH] " Kloetzke Jan
2019-04-30 14:08 ` Kloetzke Jan
2019-04-30 14:15 ` [PATCH v2] " Kloetzke Jan
2019-04-30 14:15 ` [v2] " Kloetzke Jan
2019-05-05 7:45 ` [PATCH v2] " David Miller
2019-05-05 7:45 ` [v2] " David Miller
2019-05-06 8:17 ` [PATCH v2] " Oliver Neukum
2019-05-16 7:10 ` Kloetzke Jan
2019-05-21 0:09 ` David Miller
2019-05-21 9:48 ` Oliver Neukum
2019-05-21 10:12 ` Kloetzke Jan
2019-05-21 11:42 ` Oliver Neukum [this message]
2019-05-21 13:18 ` [PATCH v3] " Kloetzke Jan
2019-05-21 20:47 ` David Miller
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=1558438944.12672.13.camel@suse.com \
--to=oneukum@suse.com \
--cc=Jan.Kloetzke@preh.de \
--cc=davem@davemloft.net \
--cc=jan@kloetzke.net \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@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 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.