From: Greg KH <greg@kroah.com>
To: Nishanth Aravamudan <nacc@us.ibm.com>
Cc: gregkh@us.ibm.com, marcel@holtmann.org, maxk@qualcomm.com,
jt@hpl.hp.com, perex@suse.cz, linux-dvb-maintainer@linuxtv.org,
johnpol@2ka.mipt.ru, linux-usb-devel@lists.sourceforge.net,
bluez-devel@lists.sourceforge.net,
irda-users@lists.sourceforge.net, alsa-devel@alsa-project.org,
linux-dvb@linuxtv.org, sensors@stimpy.netroedge.com
Subject: Re: [linux-usb-devel] [PATCH 1/63] usb/message: make usb_{control,bulk}_msg() use msecs
Date: Tue, 15 Feb 2005 14:29:38 -0800 [thread overview]
Message-ID: <20050215222937.GA16488@kroah.com> (raw)
In-Reply-To: <20050209001232.GC5661@us.ibm.com>
On Tue, Feb 08, 2005 at 04:12:32PM -0800, Nishanth Aravamudan wrote:
> Hi,
>
> Sent to everyone so that build and compile tests will be possible. Only Greg
> should need to pull this into a tree, though, to send upstream.
Ugh, 63+ patches...
Anyway, I've applied all of these, and your additional one, to my tree.
If you could make sure and check the next -mm release to make sure I got
them all, I'd appreciate it.
thanks a lot for your work, I appreciate it.
greg k-h
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
next prev parent reply other threads:[~2005-02-15 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 0:12 [PATCH 1/63] usb/message: make usb_{control,bulk}_msg() use msecs Nishanth Aravamudan
2005-02-15 22:29 ` Greg KH [this message]
2005-02-15 23:10 ` [linux-usb-devel] " Nishanth Aravamudan
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=20050215222937.GA16488@kroah.com \
--to=greg@kroah.com \
--cc=alsa-devel@alsa-project.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=gregkh@us.ibm.com \
--cc=irda-users@lists.sourceforge.net \
--cc=johnpol@2ka.mipt.ru \
--cc=jt@hpl.hp.com \
--cc=linux-dvb-maintainer@linuxtv.org \
--cc=linux-dvb@linuxtv.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
--cc=maxk@qualcomm.com \
--cc=nacc@us.ibm.com \
--cc=perex@suse.cz \
--cc=sensors@stimpy.netroedge.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