From: Martin KaFai Lau <kafai@fb.com>
To: netdev <netdev@vger.kernel.org>
Cc: Kernel Team <kernel-team@fb.com>
Subject: [PATCH net-next v2 0/2] ipv6: Avoid rt6_probe() taking writer lock in the fast path
Date: Fri, 24 Jul 2015 09:57:41 -0700 [thread overview]
Message-ID: <1437757063-1186401-1-git-send-email-kafai@fb.com> (raw)
v1 -> v2:
1. Separate the code re-arrangement into another patch
2. Fix style
next reply other threads:[~2015-07-24 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 16:57 Martin KaFai Lau [this message]
2015-07-24 16:57 ` [PATCH net-next v2 1/2] ipv6: Re-arrange code in rt6_probe() Martin KaFai Lau
2015-07-28 0:07 ` YOSHIFUJI Hideaki/吉藤英明
2015-07-24 16:57 ` [PATCH net-next v2 2/2] ipv6: Avoid rt6_probe() taking writer lock in the fast path Martin KaFai Lau
2015-07-28 0:17 ` YOSHIFUJI Hideaki
2015-07-27 8:08 ` [PATCH net-next v2 0/2] " 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=1437757063-1186401-1-git-send-email-kafai@fb.com \
--to=kafai@fb.com \
--cc=kernel-team@fb.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).