From: patchwork-bot+netdevbpf@kernel•org
To: Randy Dunlap <rdunlap@infradead•org>
Cc: netdev@vger•kernel.org, linux-um@lists•infradead.org,
jdike@addtoit•com, richard@nod•at,
anton.ivanov@cambridgegreys•com, davem@davemloft•net,
kuba@kernel•org, t.sailer@alumni•ethz.ch,
linux-hams@vger•kernel.org
Subject: Re: [PATCH net] hamradio: baycom_epp: fix build for UML
Date: Mon, 18 Oct 2021 12:00:06 +0000 [thread overview]
Message-ID: <163455840685.2577.7817040614905305666.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211015021804.17005-1-rdunlap@infradead.org>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft•net>:
On Thu, 14 Oct 2021 19:18:04 -0700 you wrote:
> On i386, the baycom_epp driver wants to inspect X86 CPU features (TSC)
> and then act on that data, but that info is not available when running
> on UML, so prevent that test and do the default action.
>
> Prevents this build error on UML + i386:
>
> ../drivers/net/hamradio/baycom_epp.c: In function ‘epp_bh’:
> ../drivers/net/hamradio/baycom_epp.c:630:6: error: implicit declaration of function ‘boot_cpu_has’; did you mean ‘get_cpu_mask’? [-Werror=implicit-function-declaration]
> if (boot_cpu_has(X86_FEATURE_TSC)) \
> ^
> ../drivers/net/hamradio/baycom_epp.c:658:2: note: in expansion of macro ‘GETTICK’
> GETTICK(time1);
>
> [...]
Here is the summary with links:
- [net] hamradio: baycom_epp: fix build for UML
https://git.kernel.org/netdev/net/c/0a9bb11a5e29
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-10-18 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 2:18 [PATCH net] hamradio: baycom_epp: fix build for UML Randy Dunlap
2021-10-18 12:00 ` patchwork-bot+netdevbpf [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=163455840685.2577.7817040614905305666.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=anton.ivanov@cambridgegreys$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=jdike@addtoit$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-hams@vger$(echo .)kernel.org \
--cc=linux-um@lists$(echo .)infradead.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=rdunlap@infradead$(echo .)org \
--cc=richard@nod$(echo .)at \
--cc=t.sailer@alumni$(echo .)ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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