From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754246AbYEAB4c (ORCPT ); Wed, 30 Apr 2008 21:56:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754717AbYEAB4I (ORCPT ); Wed, 30 Apr 2008 21:56:08 -0400 Received: from wa-out-1112.google.com ([209.85.146.178]:62830 "EHLO wa-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754389AbYEAB4G (ORCPT ); Wed, 30 Apr 2008 21:56:06 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=U4KqN1nelG3bvG56BJpQQg/t7RR1HZdFqhEcHNiEX1u1D/qoOJiYxCgntKfEIVZt0ZhHKmCgGgjqC+EhnI7eGmdEswGqKQvbkCdwQRa2Ja+KOwNvhBmbjkhKFXABhGAks2Y28kezzspecnd3mvpJaQLTHBZnC7QWAjCB4RXO1a0= Message-ID: Date: Wed, 30 Apr 2008 18:56:05 -0700 From: "SL Baur" To: "Greg KH" Subject: Re: patch usb-mos7840-test-and-propagate-set_uart_reg-return-value.patch added to gregkh-2.6 tree Cc: 12o3l@tiscali.nl, greg@kroah.com, linux-kernel@vger.kernel.org In-Reply-To: <20080430060359.GB10457@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4806CF18.2050403@tiscali.nl> <12094267913945@kroah.org> <20080429065133.GA8708@suse.de> <20080430060359.GB10457@suse.de> X-Google-Sender-Auth: 15d047e722f0a15d Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/29/08, Greg KH wrote: > On Tue, Apr 29, 2008 at 12:33:39AM -0700, SL Baur wrote: > > On 4/28/08, Greg KH wrote: > > > On Mon, Apr 28, 2008 at 11:31:07PM -0700, SL Baur wrote: > > > > > Does that mean that the original patch is invalid? Or just that your > > > question was never answered? > > > > I think there are more of the same issues that the patch > > addressed in the same file and the patcher never responded > > back about that. > > > But again, is the current patch somehow not valid? No, it's fine. -sb