From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753435Ab2KPTkK (ORCPT ); Fri, 16 Nov 2012 14:40:10 -0500 Received: from terminus.zytor.com ([198.137.202.10]:35493 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753193Ab2KPTkH (ORCPT ); Fri, 16 Nov 2012 14:40:07 -0500 Message-ID: <50A69684.20103@zytor.com> Date: Fri, 16 Nov 2012 11:39:48 -0800 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121029 Thunderbird/16.0.2 MIME-Version: 1.0 To: Yinghai Lu CC: Thomas Gleixner , Ingo Molnar , linux-kernel@vger.kernel.org, Matt Fleming Subject: Re: [PATCH 8/9] x86: ramdisk info print with high bits. References: <1353055989-31939-1-git-send-email-yinghai@kernel.org> <1353055989-31939-9-git-send-email-yinghai@kernel.org> <50A6644D.80205@zytor.com> In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/16/2012 11:32 AM, Yinghai Lu wrote: >> >> or fix printk to add extra 2 for "0x" when # is found? > > looks like we have lots of %#010llx or %#010Lx there in arch/x86. > > We need to fix printk to make it acting like %pR ? > No, it was a thinko on my part. -hpa