From: Oliver Neukum <oneukum@suse.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: netdev@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [REPOST PATCH] net/usbnet: avoid recursive locking in usbnet_stop()
Date: Thu, 8 Mar 2012 09:38:17 +0100 [thread overview]
Message-ID: <201203080938.17604.oneukum@suse.de> (raw)
In-Reply-To: <20120307201928.GA30188@linutronix.de>
Am Mittwoch, 7. März 2012, 21:19:28 schrieb Sebastian Andrzej Siewior:
> Cc: stable@kernel.org
> Reported-by: AnÃbal Almeida Pinto <anibal.pinto@efacec.com>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Acked-by: Oliver Neukum <oliver@neukum.org>
next prev parent reply other threads:[~2012-03-08 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 20:19 [REPOST PATCH] net/usbnet: avoid recursive locking in usbnet_stop() Sebastian Andrzej Siewior
2012-03-08 8:38 ` Oliver Neukum [this message]
[not found] ` <201203080938.17604.oneukum-l3A5Bk7waGM@public.gmane.org>
2012-03-08 8:50 ` 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=201203080938.17604.oneukum@suse.de \
--to=oneukum@suse.de \
--cc=bigeasy@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).