From: David Miller <davem@davemloft.net>
To: machida.yuki@jp.fujitsu.com
Cc: netdev@vger.kernel.org, hideaki.yoshifuji@miraclelinux.com,
yoshfuji@linux-ipv6.org, liuhangbin@gmail.com
Subject: Re: [PATCH stable v2 1/1] net/ipv6: add sysctl option accept_ra_min_hop_limit
Date: Fri, 19 Feb 2016 11:14:23 -0500 (EST) [thread overview]
Message-ID: <20160219.111423.805323521899765528.davem@davemloft.net> (raw)
In-Reply-To: <56C6D736.20901@jp.fujitsu.com>
From: Yuki Machida <machida.yuki@jp.fujitsu.com>
Date: Fri, 19 Feb 2016 17:49:58 +0900
> ping? thanks.
If your patch is properly queued in patchwork, you never need to do
pings on the mailing list like this.
Someone knows the patch need to be dealt with, and if it is not being
reviewed it simply means that other patches are other older or have
a much higher priority than your's.
prev parent reply other threads:[~2016-02-19 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 1:56 [PATCH stable v2 1/1] net/ipv6: add sysctl option accept_ra_min_hop_limit Yuki Machida
2016-02-19 8:49 ` Yuki Machida
2016-02-19 16:14 ` 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=20160219.111423.805323521899765528.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hideaki.yoshifuji@miraclelinux.com \
--cc=liuhangbin@gmail.com \
--cc=machida.yuki@jp.fujitsu.com \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).