From: patchwork-bot+netdevbpf@kernel.org
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: przemyslaw.kitszel@intel.com, naresh.kamboju@linaro.org,
linux-kernel@vger.kernel.org,
nxne.cnse.osdt.itp.upstreaming@intel.com, andrew+netdev@lunn.ch,
edumazet@google.com, netdev@vger.kernel.org,
anthony.l.nguyen@intel.com, horms@kernel.org, kuba@kernel.org,
michal.swiatkowski@linux.intel.com, pabeni@redhat.com,
davem@davemloft.net, intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [PATCH net-next] libie: fix linking with libie_{adminq, fwlog} when CONFIG_LIBIE=n
Date: Tue, 16 Sep 2025 23:30:06 +0000 [thread overview]
Message-ID: <175806540601.1398896.2078220430438993284.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250916160118.2209412-1-aleksander.lobakin@intel.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 16 Sep 2025 18:01:18 +0200 you wrote:
> Initially, libie contained only 1 module and I assumed that new modules
> in its folder would depend on it.
> However, Michał did a good job and libie_{adminq,fwlog} are completely
> independent, but libie/ is still traversed by Kbuild only under
> CONFIG_LIBIE != n.
> This results in undefined references with certain kernel configs.
>
> [...]
Here is the summary with links:
- [net-next] libie: fix linking with libie_{adminq,fwlog} when CONFIG_LIBIE=n
https://git.kernel.org/netdev/net-next/c/5ed994dd0b7b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
michal.swiatkowski@linux.intel.com, przemyslaw.kitszel@intel.com,
anthony.l.nguyen@intel.com, horms@kernel.org, lkp@intel.com,
naresh.kamboju@linaro.org,
nxne.cnse.osdt.itp.upstreaming@intel.com,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] libie: fix linking with libie_{adminq,fwlog} when CONFIG_LIBIE=n
Date: Tue, 16 Sep 2025 23:30:06 +0000 [thread overview]
Message-ID: <175806540601.1398896.2078220430438993284.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250916160118.2209412-1-aleksander.lobakin@intel.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 16 Sep 2025 18:01:18 +0200 you wrote:
> Initially, libie contained only 1 module and I assumed that new modules
> in its folder would depend on it.
> However, Michał did a good job and libie_{adminq,fwlog} are completely
> independent, but libie/ is still traversed by Kbuild only under
> CONFIG_LIBIE != n.
> This results in undefined references with certain kernel configs.
>
> [...]
Here is the summary with links:
- [net-next] libie: fix linking with libie_{adminq,fwlog} when CONFIG_LIBIE=n
https://git.kernel.org/netdev/net-next/c/5ed994dd0b7b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-09-16 23:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 16:01 [Intel-wired-lan] [PATCH net-next] libie: fix linking with libie_{adminq, fwlog} when CONFIG_LIBIE=n Alexander Lobakin
2025-09-16 16:01 ` [PATCH net-next] libie: fix linking with libie_{adminq,fwlog} " Alexander Lobakin
2025-09-16 17:50 ` [Intel-wired-lan] [PATCH net-next] libie: fix linking with libie_{adminq, fwlog} " Tony Nguyen
2025-09-16 17:50 ` [PATCH net-next] libie: fix linking with libie_{adminq,fwlog} " Tony Nguyen
2025-09-16 19:04 ` [Intel-wired-lan] [PATCH net-next] libie: fix linking with libie_{adminq, fwlog} " Vadim Fedorenko
2025-09-16 19:04 ` [PATCH net-next] libie: fix linking with libie_{adminq,fwlog} " Vadim Fedorenko
2025-09-16 23:30 ` patchwork-bot+netdevbpf [this message]
2025-09-16 23:30 ` patchwork-bot+netdevbpf
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=175806540601.1398896.2078220430438993284.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.swiatkowski@linux.intel.com \
--cc=naresh.kamboju@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=nxne.cnse.osdt.itp.upstreaming@intel.com \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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.