From: Greg KH <greg@kroah.com>
To: Romit Dasgupta <romlinux@gmail.com>
Cc: David Brownell <david-b@pacbell.net>,
stern@rowland.harvard.edu, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Moving spinlock to struct usb_hcd
Date: Sun, 27 Jan 2008 20:24:49 -0800 [thread overview]
Message-ID: <20080128042449.GA6374@kroah.com> (raw)
In-Reply-To: <9f29ca150801272020t2ced46b6ka8e7890dfbe1e1a8@mail.gmail.com>
On Mon, Jan 28, 2008 at 09:50:36AM +0530, Romit Dasgupta wrote:
> Hi,
> Should I go ahead and submit the patch with the usual
> "signed-off" thingie? Or is it totally useless patch that is going to
> be ignored?
Let's see some proof that it actually helps, and then we can evaluate if
it is needed or not :)
thanks,
greg k-h
prev parent reply other threads:[~2008-01-28 4:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 6:30 [PATCH] Moving spinlock to struct usb_hcd Romit Dasgupta
2008-01-26 8:21 ` David Brownell
2008-01-26 15:36 ` Romit Dasgupta
2008-01-28 4:20 ` Romit Dasgupta
2008-01-28 4:24 ` 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=20080128042449.GA6374@kroah.com \
--to=greg@kroah.com \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=romlinux@gmail.com \
--cc=stern@rowland.harvard.edu \
/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