From: Steffen Klassert <steffen.klassert@secunet.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: <netdev@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Sabrina Dubroca <sd@queasysnail.net>
Subject: Re: [PATCH ipsec] esp4: improve xfrm4_beet_gso_segment() to be more readable
Date: Tue, 19 May 2020 10:50:45 +0200 [thread overview]
Message-ID: <20200519085045.GD13121@gauss3.secunet.de> (raw)
In-Reply-To: <ad586dda50caf7a29cb1d8b760d38d550a662bc9.1589780119.git.lucien.xin@gmail.com>
On Mon, May 18, 2020 at 01:35:19PM +0800, Xin Long wrote:
> This patch is to improve the code to make xfrm4_beet_gso_segment()
> more readable, and keep consistent with xfrm6_beet_gso_segment().
>
> Signed-off-by: Xin Long <lucien.xin@gmail.com>
Applied, thanks Xin!
prev parent reply other threads:[~2020-05-19 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 5:35 [PATCH ipsec] esp4: improve xfrm4_beet_gso_segment() to be more readable Xin Long
2020-05-19 8:50 ` 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=20200519085045.GD13121@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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).