From: Al Viro <viro@zeniv.linux.org.uk>
To: Xin Gao <gaoxin@cdjrlc.com>
Cc: dhowells@redhat.com, jarkko@kernel.org, jmorris@namei.org,
serge@hallyn.com, keyrings@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KEYS: Variable type completion
Date: Tue, 16 Aug 2022 19:14:23 +0100 [thread overview]
Message-ID: <Yvvef4vCFaYhMjMq@ZenIV> (raw)
In-Reply-To: <20220816180110.8625-1-gaoxin@cdjrlc.com>
On Wed, Aug 17, 2022 at 02:01:10AM +0800, Xin Gao wrote:
> 'unsigned int' is better than 'unsigned'.
Explain.
You keep sending rather pointless patches with declarative
commit messages instead of explanations. Why is 'unsigned
int' better than 'unsigned'? Demonstrate understanding -
simple reference to checkpatch.pl does *NOT* count.
next prev parent reply other threads:[~2022-08-16 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 18:01 [PATCH] KEYS: Variable type completion Xin Gao
2022-08-16 18:14 ` Al Viro [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-16 18:04 [PATCH] keys: " Xin Gao
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=Yvvef4vCFaYhMjMq@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=dhowells@redhat.com \
--cc=gaoxin@cdjrlc.com \
--cc=jarkko@kernel.org \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.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