From: Jakub Kicinski <kuba@kernel.org>
To: "Zou, Steven" <steven.zou@intel.com>
Cc: "Sharma, Mayank" <mayank.sharma@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Staikov, Andrii" <andrii.staikov@intel.com>,
"Lobakin, Aleksander" <aleksander.lobakin@intel.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"horms@kernel.org" <horms@kernel.org>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>,
"Buvaneswaran, Sujai" <sujai.buvaneswaran@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next] ice: Add switch recipe reusing feature
Date: Wed, 6 Mar 2024 07:00:54 -0800 [thread overview]
Message-ID: <20240306070054.094fe4a6@kernel.org> (raw)
In-Reply-To: <0056a010-4fd6-4300-9790-649d820a5a01@intel.com>
On Wed, 6 Mar 2024 22:55:48 +0800 Zou, Steven wrote:
> > We are seeing following kernel compilation error while compiling next kernel:
> >
> > "error: dereferencing pointer to incomplete type 'struct dpll_pin'"
>
> Thanks Mayank!
> The patch does not touch 'stuct dpll_pin', I do not think this is caused
> by the patch changes.
> And the patch is based on the base-commit:
> ce1833c065c8c9aec8b147dd682b0ddca8c30071 that I built and loaded the
> ice.ko successfully before I submitted the patch.
>
> Hi Tony,
> Do you have any suggestion about this compilation issue?
net-next tree currently has this problem. You can try merging in net
which has the fix (it will propagate to net-next on Thursday).
Or try changing the compiler, newer Clang and GCC do not generate this
error.
next prev parent reply other threads:[~2024-03-06 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 3:18 [PATCH iwl-next] ice: Add switch recipe reusing feature Steven Zou
[not found] ` <PH0PR11MB5013D1C2AD784512CA70173396212@PH0PR11MB5013.namprd11.prod.outlook.com>
2024-03-06 13:48 ` [Intel-wired-lan] " Sharma, Mayank
2024-03-06 14:55 ` Zou, Steven
2024-03-06 15:00 ` Jakub Kicinski [this message]
2024-03-20 10:38 ` Sharma, Mayank
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=20240306070054.094fe4a6@kernel.org \
--to=kuba@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=andrii.staikov@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=mayank.sharma@intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
--cc=steven.zou@intel.com \
--cc=sujai.buvaneswaran@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).