From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753598AbbL2Qmo (ORCPT ); Tue, 29 Dec 2015 11:42:44 -0500 Received: from mga09.intel.com ([134.134.136.24]:23924 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753480AbbL2Qmm (ORCPT ); Tue, 29 Dec 2015 11:42:42 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,496,1444719600"; d="scan'208";a="871287542" From: Andy Shevchenko To: Andrew Morton , Rasmus Villemoes , linux-kernel@vger.kernel.org, Joe Perches Cc: Andy Shevchenko Subject: [PATCH v2 0/2] lib/vsprintf: introduce stricter rules for %p extensions Date: Tue, 29 Dec 2015 18:42:36 +0200 Message-Id: <1451407358-7041-1-git-send-email-andriy.shevchenko@linux.intel.com> X-Mailer: git-send-email 2.6.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Besides the code refactoring we introduce the following rules for %p extensions here. i.e: - fixed type extensions are always printed in hex format, prefixed by '0x', small letters, full field width on a running architecture (%pa[dp], %pNF) - fallback to %p based on different kernel configuration will be under the same rule set as for fixed types above (%pCn when COMMON_CLK=n, %p[FfSsB] when KALLSYMS=n) - fallback to %p of unimplemented extension will be under the same rule set as for fixed types above (%pN) Since v1: - address comments from Joe and Rasmums (might be not all of them) - add patch 2 - desribe in cover letter what is done besides refactoring Andy Shevchenko (2): lib/vsprintf: refactor duplicate code to special_hex_number() lib/vsprintf: factor out %pN[F] handler as netdev_bits() lib/vsprintf.c | 70 ++++++++++++++++++++++++++++++++-------------------------- 1 file changed, 39 insertions(+), 31 deletions(-) -- 2.6.4