From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?UmFmYcWCIE1pxYJlY2tpIDx6YWplYzVAZ21haWwuY29tPg==?=@ci.codeaurora.org
Cc: andrew@lunn.ch, vivien.didelot@gmail.com, olteanv@gmail.com,
davem@davemloft.net, kuba@kernel.org, f.fainelli@gmail.com,
netdev@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com,
rafal@milecki.pl
Subject: Re: [PATCH V2] net: dsa: bcm_sf2: refactor LED regs access
Date: Fri, 31 Dec 2021 02:30:09 +0000 [thread overview]
Message-ID: <164091780950.19399.2794312145648302325.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211229171642.22942-1-zajec5@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 29 Dec 2021 18:16:42 +0100 you wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> 1. Define more regs. Some switches (e.g. BCM4908) have up to 6 regs.
> 2. Add helper for handling non-lineral port <-> reg mappings.
> 3. Add support for 12 B LED reg blocks on BCM4908 (different layout)
>
> Complete support for LEDs setup will be implemented once Linux receives
> a proper design & implementation for "hardware" LEDs.
>
> [...]
Here is the summary with links:
- [V2] net: dsa: bcm_sf2: refactor LED regs access
https://git.kernel.org/netdev/net-next/c/af30f8eaa8fe
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-12-31 2:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 22:09 [PATCH] net: dsa: bcm_sf2: refactor LED regs access Rafał Miłecki
2021-12-29 16:40 ` Florian Fainelli
2021-12-29 17:16 ` [PATCH V2] " Rafał Miłecki
2021-12-29 19:55 ` Florian Fainelli
2021-12-31 2: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=164091780950.19399.2794312145648302325.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?UmFmYcWCIE1pxYJlY2tpIDx6YWplYzVAZ21haWwuY29tPg==?=@ci.codeaurora.org \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=rafal@milecki.pl \
--cc=vivien.didelot@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.