Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751445AbdINGoM (ORCPT ); Thu, 14 Sep 2017 02:44:12 -0400 Received: from mail-pf0-f181.google.com ([209.85.192.181]:46813 "EHLO mail-pf0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750770AbdINGoK (ORCPT ); Thu, 14 Sep 2017 02:44:10 -0400 X-Google-Smtp-Source: ADKCNb6xQkkzJPEYacQ7s6ipnlQpatHeaa0hFOSMtfjkn42j950XzqpMLK4hm1iIZzlyLcP7A6hblA== Date: Thu, 14 Sep 2017 15:44:05 +0900 From: Sergey Senozhatsky To: Helge Deller Cc: Sergey Senozhatsky , "Luck, Tony" , "linux-kernel@vger.kernel.org" , Sergey Senozhatsky , Petr Mladek , Andrew Morton , "Yu, Fenghua" , Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman Subject: Re: [PATCH 00/14] Fix wrong %pF and %pS printk format specifier usages Message-ID: <20170914064405.GC599@jagdpanzerIV.localdomain> References: <8b93f9ca-95f6-4e40-1cc8-d1a65833abff@gmx.de> <20170907075653.GA533@jagdpanzerIV.localdomain> <20170907083207.GC533@jagdpanzerIV.localdomain> <667b8849-fb60-a312-2483-505252ff737e@gmx.de> <20170907093631.GD533@jagdpanzerIV.localdomain> <20170907095119.GE533@jagdpanzerIV.localdomain> <0604f27e-24ab-625b-9013-c6c0f4f6acc1@gmx.de> <3908561D78D1C84285E8C5FCA982C28F6136C2ED@ORSMSX114.amr.corp.intel.com> <20170908061830.GA496@jagdpanzerIV.localdomain> <6fdd62aa-e9e7-8954-da6b-6fa5e73983c5@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6fdd62aa-e9e7-8954-da6b-6fa5e73983c5@gmx.de> User-Agent: Mutt/1.9.0 (2017-09-02) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 753 Lines: 23 Hi, On (09/08/17 22:49), Helge Deller wrote: [..] > Sergey, I'm sure there is a way how you can get it somehow to work the way > you describe above, but even then nobody can guarantee you that it > will work in 100% of the cases. > > It's somehow like "we have %lu and %c specifiers, and it's basically > the same, so let's try to figure out at runtime which one should be > used based on analysis of what was given as argument". > It may work somehow, but not always. > > What about the idea of a %luS specifier (or something other) ? the idea is to have less format specifiers ;) %pF/%pf is a subtle ABI detail, which made it to API. I'm OK to keep %pf/%pF, if we won't be able to improve %ps/%pS. otherwise, I'd prefer to get rid of it. -ss