From: David Woodhouse <dwmw2@infradead.org>
To: Gery Kahn <gery.kahn@gmail.com>
Cc: linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
Luciano Coelho <coelho@ti.com>
Subject: Re: [PATCH] linux-firmware: Initial release for Bluetooth init script
Date: Wed, 02 Mar 2011 13:57:26 +0000 [thread overview]
Message-ID: <1299074246.24834.30.camel@macbook.infradead.org> (raw)
In-Reply-To: <1299072814-11660-1-git-send-email-geryk@ti.com>
On Wed, 2011-03-02 at 15:33 +0200, Gery Kahn wrote:
>
> WHENCE | 12 ++++++++++++
> ti-connectivity/TIInit_7.2.31.bts | Bin 0 -> 48909 bytes
Does this live in /lib/firmware or in /lib/firmware/ti-connectivity?
If the former, please don't put the actual file in a subdirectory. If
the latter, your comment in the WHENCE file is wrong.
--
dwmw2
next prev parent reply other threads:[~2011-03-02 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 13:33 [PATCH] linux-firmware: Initial release for Bluetooth init script Gery Kahn
2011-03-02 13:57 ` David Woodhouse [this message]
2011-03-02 14:28 ` Kahn, Gery
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=1299074246.24834.30.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=coelho@ti.com \
--cc=gery.kahn@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@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