From: patchwork-bot+netdevbpf@kernel.org
To: Cosmo Chou <chou.cosmo@gmail.com>
Cc: kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, sam@mendozajonas.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
cosmo.chou@quantatw.com
Subject: Re: [PATCH v2] net/ncsi: clear Tx enable mode when handling a Config required AEN
Date: Fri, 28 Apr 2023 08:40:19 +0000 [thread overview]
Message-ID: <168267121956.29185.4280925593881439460.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230426081350.1214512-1-chou.cosmo@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 26 Apr 2023 16:13:50 +0800 you wrote:
> ncsi_channel_is_tx() determines whether a given channel should be
> used for Tx or not. However, when reconfiguring the channel by
> handling a Configuration Required AEN, there is a misjudgment that
> the channel Tx has already been enabled, which results in the Enable
> Channel Network Tx command not being sent.
>
> Clear the channel Tx enable flag before reconfiguring the channel to
> avoid the misjudgment.
>
> [...]
Here is the summary with links:
- [v2] net/ncsi: clear Tx enable mode when handling a Config required AEN
https://git.kernel.org/netdev/net/c/6f75cd166a5a
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:[~2023-04-28 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 13:30 [PATCH] net/ncsi: clear Tx enable mode when handling a Config required AEN cchoux
2023-04-25 15:38 ` Jakub Kicinski
2023-04-26 8:13 ` [PATCH v2] " Cosmo Chou
2023-04-28 8: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=168267121956.29185.4280925593881439460.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=chou.cosmo@gmail.com \
--cc=cosmo.chou@quantatw.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sam@mendozajonas.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).