From: Greg KH <gregkh@suse.de>
To: linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net, zaitcev@redhat.com
Subject: Re: [PATCH] USB: fix ub issues
Date: Thu, 9 Jun 2005 10:07:20 -0700 [thread overview]
Message-ID: <20050609170720.GH9597@kroah.com> (raw)
In-Reply-To: <1118335493872@kroah.com>
On Thu, Jun 09, 2005 at 09:44:53AM -0700, Greg KH wrote:
> [PATCH] USB: fix ub issues
<snip>
> [PATCH] USB: fix ub issues
<snip>
Crap, my scripts went crazy again, due to changes in git (sure, blame
someone else...) Sorry about the "double the patch" messages.
thanks,
greg k-h
next prev parent reply other threads:[~2005-06-09 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 16:43 [GIT PATCH] USB bugfixes and a PCI one too for 2.6.12-rc6 Greg KH
2005-06-09 16:44 ` [PATCH] PCI Hotplug: fix CPCI reference counting bug Greg KH
2005-06-09 16:44 ` [PATCH] USB: fix ub issues Greg KH
2005-06-09 16:44 ` [PATCH] USB: ftdi_sio: avoid losing received data in tty-ldisc Greg KH
2005-06-09 17:07 ` Greg KH [this message]
2005-06-09 17:49 ` [GIT PATCH] USB bugfixes and a PCI one too for 2.6.12-rc6 Linus Torvalds
2005-06-09 17:52 ` Greg KH
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=20050609170720.GH9597@kroah.com \
--to=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=zaitcev@redhat.com \
/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