All of lore.kernel.org
 help / color / mirror / Atom feed
From: <sean.wang@mediatek.com>
To: <marcel@holtmann.org>
Cc: <johan.hedberg@gmail.com>, <Sean.Wang@mediatek.com>,
	<linux-bluetooth@vger.kernel.org>,
	<linux-mediatek@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <Mark-YW.Chen@mediatek.com>,
	Sean Wang <sean.wang@mediatek.com>
Subject: Re: [PATCH v2 1/2] Bluetooth: btusb: fix up firmware download sequence
Date: Tue, 23 Jun 2020 02:28:47 +0800	[thread overview]
Message-ID: <1592850527-20931-1-git-send-email-sean.wang@mediatek.com> (raw)
In-Reply-To: <5F6C2EB2-B0DF-4534-A123-4E6969A98410@holtmann.org>

From: Sean Wang <sean.wang@mediatek.com>

>Hi Sean,
>
>> From: Sean Wang <sean.wang@mediatek.com>
>>
>> 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.

>Regards
>
>Marcel

  reply	other threads:[~2020-06-22 18:29 UTC|newest]

Thread overview: 9+ 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 ` sean.wang
2020-06-19 17:52 ` [PATCH v2 2/2] Bluetooth: btmtksdio: " sean.wang
2020-06-19 17:52   ` 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 [this message]
2020-06-23 12:38     ` Marcel Holtmann
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=1592850527-20931-1-git-send-email-sean.wang@mediatek.com \
    --to=sean.wang@mediatek.com \
    --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=marcel@holtmann.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 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.