From: patchwork-bot+netdevbpf@kernel.org
To: Aaron Ma <aaron.ma@canonical.com>
Cc: nbd@nbd.name, lorenzo.bianconi83@gmail.com,
ryder.lee@mediatek.com, kvalo@codeaurora.org,
davem@davemloft.net, kuba@kernel.org, matthias.bgg@gmail.com,
sean.wang@mediatek.com, Soul.Huang@mediatek.com,
deren.wu@mediatek.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] mt76: mt7921: continue to probe driver when fw already downloaded
Date: Thu, 08 Jul 2021 20:40:04 +0000 [thread overview]
Message-ID: <162577680412.12322.7727150066013328820.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210708131710.695595-1-aaron.ma@canonical.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Thu, 8 Jul 2021 21:17:10 +0800 you wrote:
> When reboot system, no power cycles, firmware is already downloaded,
> return -EIO will break driver as error:
> mt7921e: probe of 0000:03:00.0 failed with error -5
>
> Skip firmware download and continue to probe.
>
> Signed-off-by: Aaron Ma <aaron.ma@canonical.com>
>
> [...]
Here is the summary with links:
- mt76: mt7921: continue to probe driver when fw already downloaded
https://git.kernel.org/netdev/net/c/c34269041185
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-07-08 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 13:17 [PATCH] mt76: mt7921: continue to probe driver when fw already downloaded Aaron Ma
2021-07-08 15:08 ` Deren Wu
2021-07-08 20:40 ` patchwork-bot+netdevbpf [this message]
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=162577680412.12322.7727150066013328820.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Soul.Huang@mediatek.com \
--cc=aaron.ma@canonical.com \
--cc=davem@davemloft.net \
--cc=deren.wu@mediatek.com \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi83@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=ryder.lee@mediatek.com \
--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