From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Malin Jonsson <malin.jonsson@est.tech>
Cc: Przemek Kitszel <przemyslaw.kitszel@intel.com>,
<yong.g.gu@ericsson.com>, <roland.kovacs@est.tech>,
<intel-wired-lan@osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH 1/1] idpf: Add missing dependencies
Date: Mon, 14 Jul 2025 16:32:51 +0200 [thread overview]
Message-ID: <332dedfe-d3a4-446b-8a00-8d56bc54318d@intel.com> (raw)
In-Reply-To: <f6027166-2ab1-4221-9636-7ed40f1865d3@intel.com>
From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Date: Fri, 11 Jul 2025 12:25:09 +0200
> On 7/11/25 08:47, Malin Jonsson wrote:
>> The idpf driver depends on both AUXILIARY_BUS and NET_DEVLINK, but
>> they're not selected by the Kconfig. Let's fix this so idpf builds even
>> with a stripped config.
>>
>> Reported-by: Yong Gu <yong.g.gu@ericsson.com>
>> Signed-off-by: Malin Jonsson <malin.jonsson@est.tech>
>
> Thank you for the fix!
> if you have a Link to the public report, please add it as a Closes: tag
>
> Would be also great to add a Fixes: tag with the commit that introduces
> the need for given dependency/ies
> (there should be one tag only (per your commit), if both deps were
> introduced by the very same pull request, just use the earlier commit)
>
>> ---
>> drivers/net/ethernet/intel/idpf/Kconfig | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/net/ethernet/intel/idpf/Kconfig b/drivers/net/
>> ethernet/intel/idpf/Kconfig
>> index 1f893221e2c99..5c7ce626aae16 100644
>> --- a/drivers/net/ethernet/intel/idpf/Kconfig
>> +++ b/drivers/net/ethernet/intel/idpf/Kconfig
>> @@ -8,6 +8,8 @@ config IDPF
>> select LIBETH
>> select LIBETH_CP
>> select LIBETH_IRQ
>> + select AUXILIARY_BUS
>> + select NET_DEVLINK
Uhm, idpf currently uses neither of those...
Could you give a real output with the linker being unable to resolve
auxbus and/or devlink symbols for idpf.ko?
>
> looks good, but please notice that we keep this list sorted
>
>> help
>> This driver supports Intel(R) Infrastructure Data Path Function
>> devices.
Thanks,
Olek
next prev parent reply other threads:[~2025-07-14 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 6:47 [Intel-wired-lan] [PATCH 1/1] idpf: Add missing dependencies Malin Jonsson
2025-07-11 10:25 ` Przemek Kitszel
2025-07-11 11:22 ` Malin Jonsson
2025-07-11 13:53 ` Malin Jonsson
2025-07-14 14:32 ` Alexander Lobakin [this message]
2025-07-15 11:37 ` Malin Jonsson
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=332dedfe-d3a4-446b-8a00-8d56bc54318d@intel.com \
--to=aleksander.lobakin@intel.com \
--cc=intel-wired-lan@osuosl.org \
--cc=malin.jonsson@est.tech \
--cc=przemyslaw.kitszel@intel.com \
--cc=roland.kovacs@est.tech \
--cc=yong.g.gu@ericsson.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.