From: Hangbin Liu <liuhangbin@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH wireguard-tools] src/show: remove dead offset check code
Date: Tue, 18 May 2021 09:01:12 +0800 [thread overview]
Message-ID: <YKMR2CAYY9T2P/O6@Leo-laptop-t470s> (raw)
In-Reply-To: <CAHmME9rj1dJPNneAuKB3Vx7yXUGoz5aZDD8bR53dTc8yJAUN6Q@mail.gmail.com>
On Mon, May 17, 2021 at 11:44:08AM +0200, Jason A. Donenfeld wrote:
> The compiler will optimize this out, right? In which case, I like the
> consistency, in case lines are ever reordered or copy and pasted.
Not sure if compiler will optimize. I just got the complain when do covscan
checking. I'm OK to keep the format.
Thanks
Hangbin
next prev parent reply other threads:[~2021-05-18 1:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 9:10 Hangbin Liu
2021-05-17 9:44 ` Jason A. Donenfeld
2021-05-18 1:01 ` Hangbin Liu [this message]
2021-05-18 7:14 ` Jason A. Donenfeld
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=YKMR2CAYY9T2P/O6@Leo-laptop-t470s \
--to=liuhangbin@gmail.com \
--cc=Jason@zx2c4.com \
--cc=wireguard@lists.zx2c4.com \
/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).