Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Keller <jacob.e.keller@intel.com>
To: <intel-wired-lan@osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH net-next 0/3] net/intel: fix link-time undefined reference errors
Date: Wed, 20 Sep 2023 16:31:27 -0700	[thread overview]
Message-ID: <f05c2a5b-d434-5edc-828f-4b87049d01fe@intel.com> (raw)
In-Reply-To: <20230920180745.1607563-1-aleksander.lobakin@intel.com>



On 9/20/2023 11:07 AM, Alexander Lobakin wrote:
> Recently, several link-time issues were spotted in the ethernet/intel/
> folder thanks to Kbuild bots and linux-next.
> The fixes are pretty straightforward, just some stubs and CONFIG_*
> guards, so resolve all of them in one shot and unbreak randconfig
> builds.
> 
> Alexander Lobakin (3):
>   ice: fix undefined references to ice_is_*() when
>     !CONFIG_PTP_1588_CLOCK
>   ice: fix undefined references from DPLL code when
>     !CONFIG_PTP_1588_CLOCK
>   idpf: fix undefined reference to tcp_gro_complete() when !CONFIG_INET
> 
>  drivers/net/ethernet/intel/ice/Makefile     |  5 ++---
>  drivers/net/ethernet/intel/ice/ice_main.c   |  8 ++++---
>  drivers/net/ethernet/intel/ice/ice_ptp_hw.h | 25 ++++++++++++++++++++-
>  drivers/net/ethernet/intel/idpf/idpf_txrx.c |  3 +++
>  4 files changed, 34 insertions(+), 7 deletions(-)
> 
> ---
> Directly to netdev/net-next, build bots are not happy and the next
> linux-next is approaching :s

I had alternative fixes for ice at:

https://lore.kernel.org/intel-wired-lan/20230919233435.518620-1-jacob.e.keller@intel.com/

that are slightly more invasive but bring things in line with changes I
had proposed earlier before the DPLL code got merged. See:

https://lore.kernel.org/intel-wired-lan/20230919233435.518620-1-jacob.e.keller@intel.com/

I'd obviously prefer my version of the ice changes, but I understand if
we prefer a simple more 'obvious' fix be merged now. I can spin my
changes again to cleanup/refactor in a follow up if necessary.

Thanks,
Jake
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  parent reply	other threads:[~2023-09-20 23:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20 18:07 [Intel-wired-lan] [PATCH net-next 0/3] net/intel: fix link-time undefined reference errors Alexander Lobakin
2023-09-20 18:07 ` [Intel-wired-lan] [PATCH net-next 1/3] ice: fix undefined references to ice_is_*() when !CONFIG_PTP_1588_CLOCK Alexander Lobakin
2023-09-20 23:20   ` Jacob Keller
2023-09-20 18:07 ` [Intel-wired-lan] [PATCH net-next 2/3] ice: fix undefined references from DPLL code " Alexander Lobakin
2023-09-20 23:22   ` Jacob Keller
2023-09-21 23:58   ` Vadim Fedorenko
2023-09-22 13:58     ` Alexander Lobakin
2023-09-20 18:07 ` [Intel-wired-lan] [PATCH net-next 3/3] idpf: fix undefined reference to tcp_gro_complete() when !CONFIG_INET Alexander Lobakin
2023-09-20 21:30   ` Randy Dunlap
2023-09-21  0:04     ` Jacob Keller
2023-09-21  1:30       ` Randy Dunlap
2023-10-12 15:47         ` Randy Dunlap
2023-10-12 16:13           ` Alexander Lobakin
2023-10-12 18:34           ` Keller, Jacob E
2023-10-12 23:31             ` Jakub Kicinski
2023-10-13 17:16               ` Jacob Keller
2023-09-20 23:24   ` Jacob Keller
2023-09-20 23:31 ` Jacob Keller [this message]
2023-09-21 12:52   ` [Intel-wired-lan] [PATCH net-next 0/3] net/intel: fix link-time undefined reference errors Alexander Lobakin
2023-09-21 13:04   ` Alexander Lobakin
2023-09-21  8:52 ` Przemek Kitszel

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=f05c2a5b-d434-5edc-828f-4b87049d01fe@intel.com \
    --to=jacob.e.keller@intel.com \
    --cc=intel-wired-lan@osuosl.org \
    /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