From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <linux@armlinux.org.uk>
Cc: davem@davemloft.net, kuba@kernel.org, andrew@lunn.ch,
hkallweit1@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] Clean up SFP register definitions
Date: Sat, 29 Oct 2022 05:10:18 +0000 [thread overview]
Message-ID: <166702021855.21650.6992600473736103297.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <Y1qFvaDlLVM1fHdG@shell.armlinux.org.uk>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 27 Oct 2022 14:21:01 +0100 you wrote:
> Hi,
>
> This two-part patch series cleans up the SFP register definitions by
> 1. converting them from hex to decimal, as all the definitions in the
> documents use decimal, this makes it easier to cross-reference.
> 2. moving the bit definitions for each register along side their
> register address definition
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: sfp: convert register indexes from hex to decimal
https://git.kernel.org/netdev/net-next/c/17dd361119e5
- [net-next,2/2] net: sfp: move field definitions along side register index
https://git.kernel.org/netdev/net-next/c/d83845d224a0
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:[~2022-10-29 5:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 13:21 [PATCH net-next 0/2] Clean up SFP register definitions Russell King (Oracle)
2022-10-27 13:21 ` [PATCH net-next 1/2] net: sfp: convert register indexes from hex to decimal Russell King (Oracle)
2022-10-27 14:43 ` Andrew Lunn
2022-10-27 14:46 ` Russell King (Oracle)
2022-10-27 13:21 ` [PATCH net-next 2/2] net: sfp: move field definitions along side register index Russell King (Oracle)
2022-10-27 14:43 ` Andrew Lunn
2022-10-29 5:10 ` 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=166702021855.21650.6992600473736103297.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.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 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).