Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751843AbdINJ1P (ORCPT ); Thu, 14 Sep 2017 05:27:15 -0400 Received: from mail-pg0-f66.google.com ([74.125.83.66]:35829 "EHLO mail-pg0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751516AbdINJ1O (ORCPT ); Thu, 14 Sep 2017 05:27:14 -0400 X-Google-Smtp-Source: ADKCNb6bcReKA6jG0biN55p+Q6sz1hKzWEZOSoGQsYaQR7DMddly147zp+7UJQSIbX0w6f4VZscvsQ== Date: Thu, 14 Sep 2017 18:27:09 +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: <20170914092709.GI599@jagdpanzerIV.localdomain> References: <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> <20170908172528.qc2vdtxzqh777k6o@intel.com> <67a0aad8-5412-60f8-6481-562d37995eb2@gmx.de> <20170914074044.GE599@jagdpanzerIV.localdomain> <20170914080302.GF599@jagdpanzerIV.localdomain> <404e94ca-36b3-8ea2-8ccc-e4a261b38416@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <404e94ca-36b3-8ea2-8ccc-e4a261b38416@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: 637 Lines: 18 On (09/14/17 10:39), Helge Deller wrote: [..] > The basic concept of your proposal may work, and since it will avoid such > coding issues in the future I think it's probably the best solution. > > Will you come up with a patch ? (I won't have time the next few days). > If yes,I'd be happy to test it on parisc. cool. I think I can try to come up with something. I don't have any access to affected H/W, so if I won't be able to bring up qemu images I'll be happy to just hand it over to platform maintainers: arch-s like parisc64 are way to exotic ;) my aim is a removal of %pf/%pF here. let's hear from ia64 and ppc64 guys. -ss