public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Christopher Li <chrisl@vmware.com>
Cc: linux kernel mail list <linux-kernel@vger.kernel.org>,
	linux-usb-devel@lists.sourceforge.net,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [patch] bug fix in usbdevfs
Date: Fri, 8 Apr 2005 11:33:14 -0700	[thread overview]
Message-ID: <20050408183314.GD18987@kroah.com> (raw)
In-Reply-To: <20050331005123.GA541@64m.dyndns.org>

On Wed, Mar 30, 2005 at 07:51:23PM -0500, Christopher Li wrote:
> Hi,
> 
> I am sorry that the last patch about 32 bit compat ioctl on
> 64 bit kernel actually breaks the usbdevfs. That is on the current
> BK tree. I am retarded. 
> 
> Here is the patch to fix it. Tested with USB hard disk and webcam
> in both 32bit compatible mode and native 64bit mode.
> 
> Again, sorry about that.

Applied, thanks.

greg k-h

      reply	other threads:[~2005-04-08 18:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-31  0:51 [patch] bug fix in usbdevfs Christopher Li
2005-04-08 18:33 ` Greg KH [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050408183314.GD18987@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=chrisl@vmware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox