Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Yugui <wangyugui@e16-tech.com>
To: intel-wired-lan@lists.osuosl.org
Subject: [Intel-wired-lan] irdma of kernel 5.15.147 compile error when in-bracnh ice is placed by 1.13.7/1.12.18
Date: Sat, 17 Feb 2024 18:59:45 +0800	[thread overview]
Message-ID: <20240217185944.28C9.409509F4@e16-tech.com> (raw)

Hi,

When  kernel 5.15.147 in-branch ice is placed by ice-1.13.7/1.12.18
- ice.ko is OK to build
- irdma failed to build

In file included from drivers/infiniband/hw/irdma/../../../net/ethernet/intel/ice/ice.h:84,
                 from drivers/infiniband/hw/irdma/main.c:4:
drivers/infiniband/hw/irdma/../../../net/ethernet/intel/ice/ice_idc_int.h:14:31: warning: 'struct iidc_core_dev_info' declared inside parameter list will not be visible outside of this definition or declaration
 *ice_get_auxiliary_drv(struct iidc_core_dev_info *cdev_info);
                               ^~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/irdma/../../../net/ethernet/intel/ice/ice_idc_int.h:15:43: warning: 'struct iidc_core_dev_info' declared inside parameter list will not be visible outside of this definition or declaration
 void ice_send_event_to_aux_no_lock(struct iidc_core_dev_info *cdev, void *data);
                                           ^~~~~~~~~~~~~~~~~~
drivers/infiniband/hw/irdma/../../../net/ethernet/intel/ice/ice_idc_int.h:17:38: warning: 'struct iidc_core_dev_info' declared inside parameter list will not be visible outside of this definition or declaration
 void ice_cdev_info_update_vsi(struct iidc_core_dev_info *cdev_info,

Any advice to fix it?
or any advice to update the ice driver of 5.15.y?

Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2024/02/02



                 reply	other threads:[~2024-02-20  0:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240217185944.28C9.409509F4@e16-tech.com \
    --to=wangyugui@e16-tech.com \
    --cc=intel-wired-lan@lists.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