From: Marcel Holtmann <marcel@holtmann.org>
To: Sean Wang <sean.wang@mediatek.com>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
linux-bluetooth@vger.kernel.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Mark-YW.Chen@mediatek.com
Subject: Re: [PATCH v2 1/2] Bluetooth: btusb: fix up firmware download sequence
Date: Tue, 23 Jun 2020 14:38:26 +0200 [thread overview]
Message-ID: <A854B681-BAFE-4FDD-9EE5-FBEF43385AA2@holtmann.org> (raw)
In-Reply-To: <1592850527-20931-1-git-send-email-sean.wang@mediatek.com>
Hi Sean,
>>> Data RAM on the device have to be powered on before starting to
>>> download the firmware.
>>>
>>> v1->v2:
>>> rebased to bluetooth-next
>>>
>>> Fixes: a1c49c434e15 ("Bluetooth: btusb: Add protocol support for
>>> MediaTek MT7668U USB devices")
>>> Co-developed-by: Mark Chen <Mark-YW.Chen@mediatek.com>
>>> Signed-off-by: Mark Chen <Mark-YW.Chen@mediatek.com>
>>> Signed-off-by: Sean Wang <sean.wang@mediatek.com>
>>> ---
>>> drivers/bluetooth/btusb.c | 16 +++++++++++++++-
>>> 1 file changed, 15 insertions(+), 1 deletion(-)
>>
>> something is fishy here. git am still fails.
>>
>
> a little weird. I will try to git format-patch and send the patch again with another machine to you.
I think it is more important that you use git send-email to ensure that patch is delivered correctly. It looks like it got base64 encoded for no reason.
Regards
Marcel
next prev parent reply other threads:[~2020-06-23 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 17:52 [PATCH v2 1/2] Bluetooth: btusb: fix up firmware download sequence sean.wang
2020-06-19 17:52 ` [PATCH v2 2/2] Bluetooth: btmtksdio: " sean.wang
2020-06-23 12:38 ` Marcel Holtmann
2020-06-22 7:15 ` [PATCH v2 1/2] Bluetooth: btusb: " Marcel Holtmann
2020-06-22 18:28 ` sean.wang
2020-06-23 12:38 ` Marcel Holtmann [this message]
2020-06-23 12:38 ` Marcel Holtmann
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=A854B681-BAFE-4FDD-9EE5-FBEF43385AA2@holtmann.org \
--to=marcel@holtmann.org \
--cc=Mark-YW.Chen@mediatek.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=sean.wang@mediatek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).