From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Jakub Kicinski <kuba@kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: torvalds@linux-foundation.org, davem@davemloft.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, netfilter-devel@vger.kernel.org,
linux-can@vger.kernel.org
Subject: Re: 32bit x86 build broken (was: Re: [GIT PULL] Networking for 5.16-rc1)
Date: Thu, 11 Nov 2021 18:50:02 -0800 [thread overview]
Message-ID: <3fc8f690b25cca5b86f23c8285fd9e90d76c9e96.camel@linux.intel.com> (raw)
In-Reply-To: <20211111174654.3d1f83e3@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On Thu, 2021-11-11 at 17:46 -0800, Jakub Kicinski wrote:
> On Thu, 11 Nov 2021 23:09:07 +0000 pr-tracker-bot@kernel.org wrote:
> > The pull request you sent on Thu, 11 Nov 2021 08:33:01 -0800:
> >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git
> > > tags/net-5.16-rc1
> >
> > has been merged into torvalds/linux.git:
> > https://git.kernel.org/torvalds/c/f54ca91fe6f25c2028f953ce82f19ca2ea0f07bb
>
> Rafael, Srinivas, we're getting 32 bit build failures after pulling
> back
> from Linus today.
>
> make[1]: *** [/home/nipa/net/Makefile:1850: drivers] Error 2
> make: *** [Makefile:219: __sub-make] Error 2
> ../drivers/thermal/intel/int340x_thermal/processor_thermal_mbox.c: In
> function ‘send_mbox_cmd’:
> ../drivers/thermal/intel/int340x_thermal/processor_thermal_mbox.c:79:37
> : error: implicit declaration of function ‘readq’; did you mean
> ‘readl’? [-Werror=implicit-function-declaration]
> 79 | *cmd_resp = readq((void __iomem *)
> (proc_priv->mmio_base + MBOX_OFFSET_DATA));
> | ^~~~~
> | readl
>
> Is there an ETA on getting this fixed?
There is already a patch submitted titled "thermal/drivers/int340x:
limit Kconfig to 64-bit""
Thanks,
Srinivas
>
prev parent reply other threads:[~2021-11-12 2:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 16:33 [GIT PULL] Networking for 5.16-rc1 Jakub Kicinski
2021-11-11 23:09 ` pr-tracker-bot
2021-11-12 1:46 ` 32bit x86 build broken (was: Re: [GIT PULL] Networking for 5.16-rc1) Jakub Kicinski
2021-11-12 2:46 ` YueHaibing
2021-11-12 2:48 ` Linus Torvalds
2021-11-12 14:33 ` Jakub Kicinski
2021-11-12 15:04 ` Srinivas Pandruvada
2021-11-13 8:46 ` Daniel Lezcano
2021-11-16 17:19 ` Rafael J. Wysocki
2021-11-12 20:44 ` Linus Torvalds
2021-11-12 2:50 ` Srinivas Pandruvada [this message]
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=3fc8f690b25cca5b86f23c8285fd9e90d76c9e96.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).