From: David Miller <davem@davemloft.net>
To: fan.du@windriver.com
Cc: fengguang.wu@intel.com, Priyanka.Jain@freescale.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: suspicious RCU usage in xfrm_net_init()
Date: Thu, 16 Aug 2012 19:39:56 -0700 (PDT) [thread overview]
Message-ID: <20120816.193956.526349200422426116.davem@davemloft.net> (raw)
In-Reply-To: <502D9938.2010908@windriver.com>
From: Fan Du <fan.du@windriver.com>
Date: Fri, 17 Aug 2012 09:07:04 +0800
> Could you please pick up this patch?
Done, but could you please put proper prefixes in your commit
message subject lines? I had to prepend "xfrm: " this time.
prev parent reply other threads:[~2012-08-17 2:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 7:37 suspicious RCU usage in xfrm_net_init() Fengguang Wu
2012-08-16 9:36 ` Fan Du
2012-08-16 15:19 ` Fengguang Wu
2012-08-17 1:07 ` Fan Du
2012-08-17 1:34 ` Paul Gortmaker
2012-08-17 2:03 ` Fan Du
2012-08-17 2:41 ` David Miller
2012-08-17 2:39 ` 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=20120816.193956.526349200422426116.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Priyanka.Jain@freescale.com \
--cc=fan.du@windriver.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@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).