From: Marcel Holtmann <marcel@holtmann.org>
To: Kiran K <kiran.k@intel.com>
Cc: linux-bluetooth@vger.kernel.org, ravishankar.srivatsa@intel.com,
chethan.tumkur.narayan@intel.com, sathish.narasimman@intel.com
Subject: Re: [PATCH v8 4/5] Bluetooth: btusb: Helper function to download firmware to Intel adapters
Date: Thu, 3 Dec 2020 14:55:09 +0100 [thread overview]
Message-ID: <044292D8-B4B8-4FE4-A52D-44A892A860D7@holtmann.org> (raw)
In-Reply-To: <20201119113943.13839-4-kiran.k@intel.com>
Hi Kiran,
> Define a helper function to download firmware for new generation Intel
> controllers
>
> Signed-off-by: Kiran K <kiran.k@intel.com>
> ---
> drivers/bluetooth/btusb.c | 165 ++++++++++++++++++++++++++++++++++++++
> 1 file changed, 165 insertions(+)
Patch has been applied to bluetooth-next tree.
Regards
Marcel
next prev parent reply other threads:[~2020-12-03 13:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 11:39 [PATCH v8 1/5] Bluetooth: btintel: Fix endianness issue for TLV version information Kiran K
2020-11-19 11:39 ` [PATCH v8 2/5] Bluetooth: btusb: Add *setup* function for new generation Intel controllers Kiran K
2020-12-03 13:53 ` Marcel Holtmann
2020-11-19 11:39 ` [PATCH v8 3/5] Bluetooth: btusb: Define a function to construct firmware filename Kiran K
2020-12-03 13:55 ` Marcel Holtmann
2020-11-19 11:39 ` [PATCH v8 4/5] Bluetooth: btusb: Helper function to download firmware to Intel adapters Kiran K
2020-12-03 13:55 ` Marcel Holtmann [this message]
2020-11-19 11:39 ` [PATCH v8 5/5] Bluetooth: btusb: Map Typhoon peak controller to BTUSB_INTEL_NEWGEN Kiran K
2020-12-03 13:54 ` Marcel Holtmann
2020-11-21 1:31 ` [v8,1/5] Bluetooth: btintel: Fix endianness issue for TLV version information bluez.test.bot
2020-12-03 13:55 ` [PATCH v8 1/5] " Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2020-11-19 11:34 Kiran K
2020-11-19 11:34 ` [PATCH v8 4/5] Bluetooth: btusb: Helper function to download firmware to Intel adapters Kiran K
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=044292D8-B4B8-4FE4-A52D-44A892A860D7@holtmann.org \
--to=marcel@holtmann.org \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ravishankar.srivatsa@intel.com \
--cc=sathish.narasimman@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.