From: Heiner Kallweit <hkallweit1@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
nic_swsd@realtek.com,
Network Development <netdev@vger.kernel.org>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
Lee Jones <lee@kernel.org>, Pavel Machek <pavel@ucw.cz>
Subject: Re: linux-next: Tree for Jan 2 (net/ethernet/realtek/r8169)
Date: Tue, 2 Jan 2024 20:56:19 +0100 [thread overview]
Message-ID: <d8fc6f4f-7458-4c67-a6e1-5a917ad95507@gmail.com> (raw)
In-Reply-To: <a80c1568-7742-4938-a460-d8a5170ae24b@infradead.org>
On 02.01.2024 18:02, Randy Dunlap wrote:
>
>
> On 1/1/24 21:57, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20231222:
>>
>
> on ppc32:
>
> when CONFIG_R8169=y and
> CONFIG_LEDS_TRIGGER_NETDEV=m, this part of the
> r8169 Makefile doesn't work as needed:
>
> ifdef CONFIG_LEDS_TRIGGER_NETDEV
> r8169-objs += r8169_leds.o
> endif
>
> causing
>
> r8169_leds.c:(.text+0x97c): undefined reference to `devm_led_classdev_register_ext'
>
>
> Full randconfig file is attached.
>
Thanks for the report. The issue is known and a fix has been submitted.
It's just not reviewed/applied yet.
https://lore.kernel.org/linux-leds/0f6f432b-c650-4bb8-a1b5-fe3372804d52@gmail.com/T/#u
next prev parent reply other threads:[~2024-01-02 19:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 5:57 linux-next: Tree for Jan 2 Stephen Rothwell
2024-01-02 17:02 ` linux-next: Tree for Jan 2 (net/ethernet/realtek/r8169) Randy Dunlap
2024-01-02 19:56 ` Heiner Kallweit [this message]
2024-01-02 17:15 ` linux-next: Tree for Jan 2 (riscv: exittext undef. references) Randy Dunlap
2024-01-02 17:15 ` Randy Dunlap
2024-01-04 11:02 ` Alexandre Ghiti
2024-01-04 11:02 ` Alexandre Ghiti
2024-01-02 18:07 ` linux-next: Tree for Jan 2 (riscv & KVM problem) Randy Dunlap
2024-01-02 18:07 ` Randy Dunlap
2024-01-03 15:18 ` Andrew Jones
2024-01-03 15:18 ` Andrew Jones
2024-01-04 6:06 ` Randy Dunlap
2024-01-04 6:06 ` Randy Dunlap
2024-01-04 8:44 ` Andrew Jones
2024-01-04 8:44 ` Andrew Jones
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=d8fc6f4f-7458-4c67-a6e1-5a917ad95507@gmail.com \
--to=hkallweit1@gmail.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=pavel@ucw.cz \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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.