[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4995B1E7.4070908@zytor.com>
Date: Fri, 13 Feb 2009 09:46:15 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Jaswinder Singh Rajput <jaswinder@...nel.org>
CC: Ingo Molnar <mingo@...e.hu>,
Andreas Herrmann <andreas.herrmann3@....com>,
Yinghai Lu <yinghai@...nel.org>,
Harvey Harrison <harvey.harrison@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org, David Woodhouse <dwmw2@...radead.org>
Subject: Re: [PATCH 4/7] x86: memtest: adapt log messages
Jaswinder Singh Rajput wrote:
> On Fri, 2009-02-13 at 17:53 +0100, Ingo Molnar wrote:
>> * Andreas Herrmann <andreas.herrmann3@....com> wrote:
>>
>>> +#ifdef CONFIG_X86_64
>>> + printk(KERN_CONT "\n %010llx - %010llx pattern %016llx",
>>> + t_start, t_start + t_size, cpu_to_be64(pattern));
>>> +#else
>>> + printk(KERN_CONT "\n %010llx - %010llx pattern %08x",
>>> + t_start, t_start + t_size, cpu_to_be32(pattern));
>>> +#endif
>> hm, is there really no cleaner way to do this?
>
> Can we use this:
>
> + printk(KERN_CONT "\n %010llx - %010llx pattern %016llx",
> + t_start, t_start + t_size, cpu_to_be64(pattern));
>
Only if you don't mind 8 extra zeros on 32 bits.
There are other problems with this, too. There is a KERN_CONT at the
end of it, but it starts a new line, and then doesn't have another
priority flag.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists