Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759505AbXIBV0E (ORCPT ); Sun, 2 Sep 2007 17:26:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752991AbXIBVZx (ORCPT ); Sun, 2 Sep 2007 17:25:53 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:56474 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750719AbXIBVZw (ORCPT ); Sun, 2 Sep 2007 17:25:52 -0400 Date: Mon, 3 Sep 2007 03:08:58 +0530 (IST) From: Satyam Sharma X-X-Sender: satyam@enigma.security.iitk.ac.in To: Alistair John Strachan cc: Jesper Juhl , Linux Kernel Mailing List , Thomas Winischhofer , Greg Kroah-Hartman , linux-usb-devel@lists.sourceforge.net Subject: Re: [PATCH -mm] sisusbvga: Fix bug and build warnings In-Reply-To: <200709022218.06849.alistair@devzero.co.uk> Message-ID: References: <9a8748490709021323k3d4adbddv53346aacdd66ab57@mail.gmail.com> <200709022218.06849.alistair@devzero.co.uk> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="464262402-1262612648-1188768980=:29617" Content-ID: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1803 Lines: 42 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --464262402-1262612648-1188768980=:29617 Content-Type: TEXT/PLAIN; CHARSET=iso-8859-15 Content-Transfer-Encoding: 8BIT Content-ID: On Sun, 2 Sep 2007, Alistair John Strachan wrote: > On Sunday 02 September 2007 21:23:16 Jesper Juhl wrote: > > On 02/09/07, Satyam Sharma wrote: > > > Hi Jesper, > > > > > > On Sun, 2 Sep 2007, Jesper Juhl wrote: > > > > > - if (!(interface = usb_find_interface(&sisusb_driver, > > > > > subminor))) { - dev_err(&sisusb->sisusb_dev->dev, > > > > > "Failed to find interface?n"); > > > > > > > > Odd how in your patch the line ends with "?n" but if I look in my > > > > local copy of the source tree I see "\n". > > > > > > Odd, indeed. I see correct '\n' in the mail I sent, but in your mail > > > here it's coming out wrong -- lkml.org shows badness as well. Hmmm, > > > "insert file" using ^R in alpine never gave any problems before ... > > The encoding is set to ISO-2022-JP, this is probably breaking things. ??? I have no clue how/why/when that suddenly happened. I clearly see "Content-Type: TEXT/PLAIN; charset=us-ascii" for the first mail I sent out -- but all the replies seem to have somehow got this weirdness. Will close and restart my alpine session, just in case ... thanks for heads-up, Alistair. --464262402-1262612648-1188768980=:29617-- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/