From: David Miller <davem@davemloft.net>
To: bvanassche@acm.org
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org
Subject: Re: Recent RCU changes in the networking code
Date: Fri, 20 Jan 2012 13:48:57 -0500 (EST) [thread overview]
Message-ID: <20120120.134857.1063822988966503185.davem@davemloft.net> (raw)
In-Reply-To: <CAO+b5-oqBNyXy+-a712VrnhSteVSPk8J5Om95E-ZQHtJBVgJAw@mail.gmail.com>
From: Bart Van Assche <bvanassche@acm.org>
Date: Fri, 20 Jan 2012 17:35:54 +0000
> As far as I can see commit cf778b00e96df6d64f8e21b8395d1f8a859ecdc7 is
> a fix for commit a9b3cd7f323b2e57593e7215362a7b02fc933e3a, the latter
> has been included in 3.2 but the former has not yet been sent to
> stable@vger.kernel.org. Shouldn't commit cf778b0 be sent to stable
> such that it gets included in the v3.2.x series ?
Sure.
prev parent reply other threads:[~2012-01-20 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 17:35 Recent RCU changes in the networking code Bart Van Assche
2012-01-20 18:48 ` David Miller [this message]
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=20120120.134857.1063822988966503185.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bvanassche@acm.org \
--cc=eric.dumazet@gmail.com \
--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).