From: patchwork-bot+netdevbpf@kernel•org
To: Moshe Tal <moshet@nvidia•com>
Cc: davem@davemloft•net, kuba@kernel•org, idosch@nvidia•com,
netdev@vger•kernel.org, amcohen@nvidia•com, jiri@nvidia•com,
petrm@nvidia•com, gal@nvidia•com, tariqt@nvidia•com
Subject: Re: [PATCH net] ethtool: Fix link extended state for big endian
Date: Thu, 20 Jan 2022 11:40:09 +0000 [thread overview]
Message-ID: <164267880960.20064.227719261291195.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220120095550.5056-1-moshet@nvidia.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft•net>:
On Thu, 20 Jan 2022 11:55:50 +0200 you wrote:
> The link extended sub-states are assigned as enum that is an integer
> size but read from a union as u8, this is working for small values on
> little endian systems but for big endian this always give 0. Fix the
> variable in the union to match the enum size.
>
> Fixes: ecc31c60240b ("ethtool: Add link extended state")
> Signed-off-by: Moshe Tal <moshet@nvidia•com>
> Reviewed-by: Ido Schimmel <idosch@nvidia•com>
> Tested-by: Ido Schimmel <idosch@nvidia•com>
> Reviewed-by: Gal Pressman <gal@nvidia•com>
> Reviewed-by: Amit Cohen <amcohen@nvidia•com>
>
> [...]
Here is the summary with links:
- [net] ethtool: Fix link extended state for big endian
https://git.kernel.org/netdev/net/c/e2f08207c558
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-01-20 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 9:55 [PATCH net] ethtool: Fix link extended state for big endian Moshe Tal
2022-01-20 11:40 ` patchwork-bot+netdevbpf [this message]
2022-01-20 14:43 ` Andrew Lunn
2022-01-23 9:08 ` Moshe Tal
2022-01-23 15:19 ` Andrew Lunn
2022-01-24 11:58 ` Petr Machata
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=164267880960.20064.227719261291195.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=amcohen@nvidia$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=gal@nvidia$(echo .)com \
--cc=idosch@nvidia$(echo .)com \
--cc=jiri@nvidia$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=moshet@nvidia$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=petrm@nvidia$(echo .)com \
--cc=tariqt@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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