From: Steffen Klassert <steffen.klassert@secunet.com>
To: Richard Guy Briggs <rgb@tricolour.ca>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<paul@nohats.ca>
Subject: Re: [PATCH] xfrm: fix header file comment reference to struct xfrm_replay_state_esn
Date: Fri, 9 Sep 2016 10:23:16 +0200 [thread overview]
Message-ID: <20160909082316.GY31137@gauss.secunet.com> (raw)
In-Reply-To: <20160908184223.GU8132@eclipse.tricolour.ca>
On Thu, Sep 08, 2016 at 02:42:23PM -0400, Richard Guy Briggs wrote:
> On 16/09/08, Richard Guy Briggs wrote:
> > Reported-by: Paul Wouters <paul@nohats.com>
>
> Oops, this above should read "nohats.ca".
I've fixed this up.
>
> > Signed-off-by: Richard Guy Briggs <rgb@tricolour.ca>
Applied to ipsec-next, thanks Richard!
prev parent reply other threads:[~2016-09-09 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 17:55 [PATCH] xfrm: fix header file comment reference to struct xfrm_replay_state_esn Richard Guy Briggs
2016-09-08 18:42 ` Richard Guy Briggs
2016-09-09 8:23 ` Steffen Klassert [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=20160909082316.GY31137@gauss.secunet.com \
--to=steffen.klassert@secunet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul@nohats.ca \
--cc=rgb@tricolour.ca \
/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).