From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
David Miller <davem@davemloft.net>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: Fwd: Re: [PATCH] can: usb_8dev: unregister netdev before free()ing
Date: Sat, 22 Jun 2013 09:08:17 +0200 [thread overview]
Message-ID: <51C54D61.104@hartkopp.net> (raw)
In-Reply-To: <51C4A6C5.7040609@cogentembedded.com>
Unfortunately the "Cc: stable@vger.kernel.org" was missing in the original patch.
I just wanted to make sure that it doesn't get lost for 3.9 stable.
Tnx & best regards,
Oliver
On 21.06.2013 21:17, Sergei Shtylyov wrote:
> Hello.
>
> On 06/21/2013 11:04 PM, Oliver Hartkopp wrote:
>
>> can you please integrate this patch into stable 3.9 too?
>> The usb_8dev driver was introduced in Linux 3.9 and has now been fixed in
>> DaveMs net-tree for 3.10 some days ago.
>
>> Upstream commit 4afe2156eb639e563d6ef0c2706b66ea400348b2
>
>> http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=4afe2156eb639e563d6ef0c2706b66ea400348b2
>>
>
>> I wanted to put stable@kernel.org in CC but that bounced.
>
> Because it's now at stable@vger.kernel.org. You don't need to CC it in your
> mail, just add "Cc: stable@vger.kernel.org" line to the patch header after
> signoff. Though actually, Dave Miller doesn't like this protocol and queues
> the stable patches himself.
>
>> Tnx,
>> Oliver
>
> WBR, Sergei
>
next prev parent reply other threads:[~2013-06-22 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 7:02 pull-request: can 2013-06-19 Marc Kleine-Budde
2013-06-19 7:02 ` [PATCH] can: usb_8dev: unregister netdev before free()ing Marc Kleine-Budde
2013-06-19 16:29 ` Oliver Hartkopp
2013-06-21 19:04 ` Fwd: " Oliver Hartkopp
2013-06-21 19:17 ` Sergei Shtylyov
2013-06-22 7:08 ` Oliver Hartkopp [this message]
2013-06-24 21:55 ` Greg Kroah-Hartman
2013-06-19 7:48 ` pull-request: can 2013-06-19 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=51C54D61.104@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-can@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
/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).