From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.2 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 93D78C433F5 for ; Thu, 23 Sep 2021 13:13:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 746976115A for ; Thu, 23 Sep 2021 13:13:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241141AbhIWNP3 (ORCPT ); Thu, 23 Sep 2021 09:15:29 -0400 Received: from mail.kernel.org ([198.145.29.99]:35550 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234515AbhIWNP2 (ORCPT ); Thu, 23 Sep 2021 09:15:28 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 0E34A61164; Thu, 23 Sep 2021 13:13:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1632402836; bh=b7ciuEU81I/+7+Kcf5GtQcPnxHNd6AApdTsqk+hICIc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=b6dQij5uc96X0dTcnPcoUuxkPTLbF2fN2/4Y5WaYYhXJ6M2KOCv5+18SPDtUxEOMv JhsZevCeAarVQfrdBBLKmDTCCmizljQrOD2L/1iNv8E+2eF4KifI/fsdwvO+G0uLoF PgeaGsco1S9SgPDGj0lg6aesyAuewN/oXBER2PLk= Date: Thu, 23 Sep 2021 15:13:53 +0200 From: Greg KH To: Guo Zhi Cc: nsaenz@kernel.org, peterz@infradead.org, maz@kernel.org, bsegall@google.com, rdunlap@infradead.org, airlied@redhat.com, kan liang , 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 Subject: Re: [PATCH] staging: vchip_arm: Fix misuse of %x Message-ID: References: <20210923035554.669434-1-qtxuning1999@sjtu.edu.cn> <590112814.393656.1632401860257.JavaMail.zimbra@sjtu.edu.cn> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <590112814.393656.1632401860257.JavaMail.zimbra@sjtu.edu.cn> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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