From: Luiz Angelo Daros de Luca <luizluca@gmail.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Christian Marangi <ansuelsmth@gmail.com>,
linus.walleij@linaro.org, alsi@bang-olufsen.dk, andrew@lunn.ch,
f.fainelli@gmail.com, olteanv@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
arinc.unal@arinc9.com, netdev@vger.kernel.org
Subject: Re: [RFC net-next 0/2] net: dsa: realtek: fix LED support for rtl8366rb
Date: Sat, 13 Jan 2024 11:41:29 -0300 [thread overview]
Message-ID: <CAJq09z5N+uunRB586c6OTbD7J4x8O=iXHpXjAQXVPN0b5zKEXA@mail.gmail.com> (raw)
In-Reply-To: <92eff1db-004c-4c08-9dd3-ae094d8dd316@gmail.com>
> This is addressed by the following patch, it should show up in linux-next
> after the merge window.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git/commit/?h=for-leds-next-next&id=5df2b4ed10a4ea636bb5ace99712a7d0c6226a55
Hello Heiner,
Yes, exactly that. Thanks. I wish it had appeared some days ago. :-)
Regards,
Luiz
next prev parent reply other threads:[~2024-01-13 14:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-06 18:40 [RFC net-next 0/2] net: dsa: realtek: fix LED support for rtl8366rb Luiz Angelo Daros de Luca
2024-01-06 18:40 ` [RFC net-next 1/2] net: dsa: realtek: keep default LED state in rtl8366rb Luiz Angelo Daros de Luca
2024-01-06 18:40 ` [RFC net-next 2/2] net: dsa: realtek: add LED drivers for rtl8366rb Luiz Angelo Daros de Luca
2024-01-06 19:47 ` [RFC net-next 0/2] net: dsa: realtek: fix LED support " Luiz Angelo Daros de Luca
2024-01-07 20:51 ` Christian Marangi
2024-01-08 5:47 ` Luiz Angelo Daros de Luca
2024-01-08 13:09 ` Christian Marangi
2024-01-13 4:06 ` Luiz Angelo Daros de Luca
2024-01-13 14:24 ` Luiz Angelo Daros de Luca
2024-01-13 14:31 ` Heiner Kallweit
2024-01-13 14:41 ` Luiz Angelo Daros de Luca [this message]
2024-01-07 20:16 ` Linus Walleij
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='CAJq09z5N+uunRB586c6OTbD7J4x8O=iXHpXjAQXVPN0b5zKEXA@mail.gmail.com' \
--to=luizluca@gmail.com \
--cc=alsi@bang-olufsen.dk \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=arinc.unal@arinc9.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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).