From: Greg KH <gregkh@linuxfoundation.org>
To: Guo Zhi <qtxuning1999@sjtu.edu.cn>
Cc: nsaenz@kernel.org, peterz@infradead.org, maz@kernel.org,
bsegall@google.com, rdunlap@infradead.org, airlied@redhat.com,
kan liang <kan.liang@linux.intel.com>,
odin@uged.al, bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-staging@lists.linux.dev,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: vchip_arm: Fix misuse of %x
Date: Thu, 23 Sep 2021 15:13:53 +0200 [thread overview]
Message-ID: <YUx9kdY5+Le+i29z@kroah.com> (raw)
In-Reply-To: <590112814.393656.1632401860257.JavaMail.zimbra@sjtu.edu.cn>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Thu, Sep 23, 2021 at 08:57:40PM +0800, Guo Zhi wrote:
> We should restrict kernel pointer leakage issue by using kptr_restrict.
> Therefore kernel pointers should be specified by %pK rather than %lx.
I totally agree.
What I am asking about is why is this message needed at all? Why not
just remove the whole thing? Who uses it?
thanks,
greg k-h
next prev parent reply other threads:[~2021-09-23 13:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 3:55 [PATCH] staging: vchip_arm: Fix misuse of %x Guo Zhi
2021-09-23 5:19 ` Greg KH
2021-09-23 10:20 ` Stefan Wahren
2021-09-23 12:57 ` Guo Zhi
2021-09-23 13:13 ` Greg KH [this message]
2021-09-24 2:57 ` Guo Zhi
2021-09-27 15:35 ` Greg KH
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=YUx9kdY5+Le+i29z@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=airlied@redhat.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bsegall@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=maz@kernel.org \
--cc=nsaenz@kernel.org \
--cc=odin@uged.al \
--cc=peterz@infradead.org \
--cc=qtxuning1999@sjtu.edu.cn \
--cc=rdunlap@infradead.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