From: Jaswinder Singh <jaswinder@infradead.org>
To: Andy Gospodarek <andy@greyhouse.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jeff Garzik <jeff@garzik.org>,
David Woodhouse <dwmw2@infradead.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] tehuti: use request_firmware
Date: Wed, 23 Jul 2008 00:52:09 +0530 [thread overview]
Message-ID: <1216754530.16481.2.camel@jaswinder.satnam> (raw)
In-Reply-To: <20080722173914.GH32408@gospo.rdu.redhat.com>
Hello Andy,
On Tue, 2008-07-22 at 13:39 -0400, Andy Gospodarek wrote:
> This has been on my TODO list for a while, but just haven't gotten
> around to it yet since I didn't feel like it was that crucial. Thanks
> for taking the time, Jaswinder.
Welcome :)
> Did you manage to test it?
>
No, I do not have this hardware.
> I would like to try it out before ACKing, so I'll do that tonight or
> tomorrow and post back my results.
>
Thank you,
Jaswinder Singh.
prev parent reply other threads:[~2008-07-22 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 15:50 [PATCH] tehuti: use request_firmware Jaswinder Singh
2008-07-22 17:39 ` Andy Gospodarek
2008-07-22 19:22 ` Jaswinder Singh [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=1216754530.16481.2.camel@jaswinder.satnam \
--to=jaswinder@infradead.org \
--cc=andy@greyhouse.net \
--cc=dwmw2@infradead.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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