[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YUx9kdY5+Le+i29z@kroah.com>
Date: Thu, 23 Sep 2021 15:13:53 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Guo Zhi <qtxuning1999@...u.edu.cn>
Cc: nsaenz@...nel.org, peterz@...radead.org, maz@...nel.org,
bsegall@...gle.com, rdunlap@...radead.org, airlied@...hat.com,
kan liang <kan.liang@...ux.intel.com>, odin@...d.al,
bcm-kernel-feedback-list@...adcom.com,
linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org,
linux-staging@...ts.linux.dev,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] staging: vchip_arm: Fix misuse of %x
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
Powered by blists - more mailing lists