From: Oliver Hartkopp <socketcan@hartkopp.net>
To: David Miller <davem@davemloft.net>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Netdev stable patches status
Date: Sat, 15 Feb 2014 18:42:29 +0100 [thread overview]
Message-ID: <52FFA705.2040006@hartkopp.net> (raw)
In-Reply-To: <52EE9C88.1010902@hartkopp.net>
Hello Dave,
there are many patches queued up for stable but not hitting the stable kernels
for a while now (even when they're already upstream).
http://patchwork.ozlabs.org/bundle/davem/stable/?state=*
Regards,
Oliver
On 02.02.2014 20:29, Oliver Hartkopp wrote:
> On 02.02.2014 19:00, Luis Henriques wrote:
>
>> I've just checked David Miller's net -stable queue[1] and it looks like he
>> has in fact already queued it. We usually pick his stable patches when he
>> sends them to the stable mailing list, so I guess we'll just wait for this
>> to happen.
>>
>> [1] http://patchwork.ozlabs.org/bundle/davem/stable/?state=*
>
> Hi Luis,
>
> I was not aware about Daves stable queue URL and especially not about the
> process for the end-of-life kernels. Good to know that you check the lists
> yourself for potential relevant stuff :-)
>
> Many thanks for your work!
>
> Best regards,
> Oliver
>
next prev parent reply other threads:[~2014-02-15 17:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 9:11 [PATCH stable 3.9+] can: add destructor for self generated skbs Oliver Hartkopp
2014-01-30 9:24 ` Marc Kleine-Budde
2014-01-30 23:10 ` Eric Dumazet
2014-01-31 0:27 ` David Miller
[not found] ` <20140130.162723.1124545320708055175.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2014-02-01 18:14 ` [INFO] BCM and ISOTP crashes Linux 3.11 - 3.13 when running on REAL HW CAN interfaces Oliver Hartkopp
2014-02-01 18:44 ` Marc Kleine-Budde
2014-02-02 18:00 ` Luis Henriques
2014-02-02 19:29 ` Oliver Hartkopp
2014-02-15 17:42 ` Oliver Hartkopp [this message]
2014-02-16 0:07 ` Netdev stable patches status 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=52FFA705.2040006@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=davem@davemloft.net \
--cc=linux-can@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).