From: David Woodhouse <dwmw2@infradead.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Deti Fliegl <deti@fliegl.de>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, jaswinder@infradead.org,
bunk@kernel.org
Subject: Re: [PATCH] dabusb: use request_firmware()
Date: Thu, 26 Jun 2008 00:01:54 +0100 [thread overview]
Message-ID: <1214434914.10393.21.camel@pmac.infradead.org> (raw)
In-Reply-To: <1214221558.27974.33.camel@shinybook.infradead.org>
On Mon, 2008-06-23 at 12:46 +0100, David Woodhouse wrote:
> That makes a certain amount of sense, I suppose, and would certainly
> reduce the litter of new _FIRMWARE options, as well as the pointless
> whining that some people like to repeat at _each_ patch when we default
> them to 'N'. I could do it something like below...
I've reworked the git tree to do it that way.
--
dwmw2
next prev parent reply other threads:[~2008-06-25 23:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 11:06 David Woodhouse
2008-06-23 11:20 ` Christoph Hellwig
2008-06-23 11:45 ` David Woodhouse
2008-06-25 23:01 ` David Woodhouse [this message]
2008-06-26 15:55 ` Adrian Bunk
2008-06-27 5:01 ` Greg KH
2008-06-27 12:36 ` Adrian Bunk
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=1214434914.10393.21.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=bunk@kernel.org \
--cc=deti@fliegl.de \
--cc=hch@infradead.org \
--cc=jaswinder@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.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
all inboxes | Powered by JetHome®