From: patchwork-bot+netdevbpf@kernel•org
To: Alexander Stein <alexander.stein@ew•tq-group.com>
Cc: andrew@lunn•ch, hkallweit1@gmail•com, linux@armlinux•org.uk,
davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
pabeni@redhat•com, f.fainelli@gmail•com, ansuelsmth@gmail•com,
netdev@vger•kernel.org
Subject: Re: [PATCH net-next v2 1/1] net: phy: Fix reading LED reg property
Date: Tue, 25 Apr 2023 01:30:18 +0000 [thread overview]
Message-ID: <168238621855.15904.17247622322735247331.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230424141648.317944-1-alexander.stein@ew.tq-group.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Mon, 24 Apr 2023 16:16:48 +0200 you wrote:
> 'reg' is always encoded in 32 bits, thus it has to be read using the
> function with the corresponding bit width.
>
> Fixes: 01e5b728e9e4 ("net: phy: Add a binding for PHY LEDs")
> Signed-off-by: Alexander Stein <alexander.stein@ew•tq-group.com>
> ---
> Changes in v2:
> * Explicitly do range check before assigning to u8
>
> [...]
Here is the summary with links:
- [net-next,v2,1/1] net: phy: Fix reading LED reg property
https://git.kernel.org/netdev/net-next/c/aed8fdad2152
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-25 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 14:16 [PATCH net-next v2 1/1] net: phy: Fix reading LED reg property Alexander Stein
2023-04-24 16:30 ` Andrew Lunn
2023-04-24 18:12 ` Florian Fainelli
2023-04-25 1:30 ` 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=168238621855.15904.17247622322735247331.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=alexander.stein@ew$(echo .)tq-group.com \
--cc=andrew@lunn$(echo .)ch \
--cc=ansuelsmth@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=f.fainelli@gmail$(echo .)com \
--cc=hkallweit1@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux@armlinux$(echo .)org.uk \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(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