[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <A854B681-BAFE-4FDD-9EE5-FBEF43385AA2@holtmann.org>
Date: Tue, 23 Jun 2020 14:38:26 +0200
From: Marcel Holtmann <marcel@...tmann.org>
To: Sean Wang <sean.wang@...iatek.com>
Cc: Johan Hedberg <johan.hedberg@...il.com>,
linux-bluetooth@...r.kernel.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org,
Mark-YW.Chen@...iatek.com
Subject: Re: [PATCH v2 1/2] Bluetooth: btusb: fix up firmware download
sequence
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@...iatek.com>
>>> Signed-off-by: Mark Chen <Mark-YW.Chen@...iatek.com>
>>> Signed-off-by: Sean Wang <sean.wang@...iatek.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
Powered by blists - more mailing lists