From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 20 Jan 2004 14:54:06 +0100 From: Vojtech Pavlik Subject: Re: [PATCH] missing space in printk message (was Re: 2.6.1-mm5) Message-ID: <20040120135406.GA553@ucw.cz> References: <20040120000535.7fb8e683.akpm@osdl.org> <6ur7xuzqci.fsf@zork.zork.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6ur7xuzqci.fsf@zork.zork.net> Sender: owner-linux-mm@kvack.org Return-Path: To: Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org List-ID: On Tue, Jan 20, 2004 at 01:45:01PM +0000, Sean Neakums wrote: > Against 2.6.1-mm5. > > > --- S1-mm5/drivers/input/keyboard/atkbd.c~ 2004-01-20 13:36:13.000000000 +0000 > +++ S1-mm5/drivers/input/keyboard/atkbd.c 2004-01-20 13:36:24.000000000 +0000 > @@ -279,7 +279,7 @@ > atkbd->translated ? "translated" : "raw", > atkbd->set, code, serio->phys); > if (atkbd->translated && atkbd->set == 2 && code == 0x7a) > - printk(KERN_WARNING "atkbd.c: This is an XFree86 bug. It shouldn't access" > + printk(KERN_WARNING "atkbd.c: This is an XFree86 bug. It shouldn't access " > "hardware directly.\n"); > else > printk(KERN_WARNING "atkbd.c: Use 'setkeycodes %s%02x ' to make it known.\n", code & 0x80 ? "e0" : "", code & 0x7f); Fixed already in my version. Thanks for pointing it out. Other than that, does keyboard work OK for you? -- Vojtech Pavlik SuSE Labs, SuSE CR -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: aart@kvack.org