From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Cc: greg@kroah.com, eric.dumazet@gmail.com, roland@kernel.org
Subject: [PATCH 0/13 net-3.1-stable] Stable queue for 3.1.5
Date: Tue, 06 Dec 2011 16:32:50 -0500 (EST) [thread overview]
Message-ID: <20111206.163250.709413251193958704.davem@davemloft.net> (raw)
[ Greg, I'm only CC:'ing you on this posting just as a FYI that
"networking stuff is coming" and nothing more, please hit delete
now, kthx, bye :-) ]
Hey guys, we have an interesting arrangement of interdependent patches
that need to go into -stable for 3.1.x so I decided to post what I have
queued up to solicit feedback.
The primary purpose of this series posting is to get reviewers to find
integration and merge errors I've made.
Eric, I incorporated Flavio's redirect fix even though it gets redone
by your version in a subsequent patch. This was intentional so that
the backports are easier to validate.
Roland, I'm incorporating the dst_get_neighbour() lockdep splt fix from
Eric to the IB layer so that we can kill all of that fallout in this
series. I hope you don't mind.
Thanks.
reply other threads:[~2011-12-06 21:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20111206.163250.709413251193958704.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=greg@kroah.com \
--cc=netdev@vger.kernel.org \
--cc=roland@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).