All of lore.kernel.org
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH net-next] net: fealnx: fix build for UML
Date: Fri, 15 Oct 2021 02:30:08 +0000	[thread overview]
Message-ID: <163426500848.31820.18368368881396978501.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211014050500.5620-1-rdunlap@infradead.org>

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 13 Oct 2021 22:05:00 -0700 you wrote:
> On i386, when builtin (not a loadable module), the fealnx driver
> inspects boot_cpu_data to see what CPU family it is running on, and
> then acts on that data. The "family" struct member (x86) does not exist
> when running on UML, so prevent that test and do the default action.
> 
> Prevents this build error on UML + i386:
> 
> [...]

Here is the summary with links:
  - [net-next] net: fealnx: fix build for UML
    https://git.kernel.org/netdev/net-next/c/cd2621d07d51

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
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
Subject: Re: [PATCH net-next] net: fealnx: fix build for UML
Date: Fri, 15 Oct 2021 02:30:08 +0000	[thread overview]
Message-ID: <163426500848.31820.18368368881396978501.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211014050500.5620-1-rdunlap@infradead.org>

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 13 Oct 2021 22:05:00 -0700 you wrote:
> On i386, when builtin (not a loadable module), the fealnx driver
> inspects boot_cpu_data to see what CPU family it is running on, and
> then acts on that data. The "family" struct member (x86) does not exist
> when running on UML, so prevent that test and do the default action.
> 
> Prevents this build error on UML + i386:
> 
> [...]

Here is the summary with links:
  - [net-next] net: fealnx: fix build for UML
    https://git.kernel.org/netdev/net-next/c/cd2621d07d51

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um


  reply	other threads:[~2021-10-15  2:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14  5:05 [PATCH net-next] net: fealnx: fix build for UML Randy Dunlap
2021-10-14  5:05 ` Randy Dunlap
2021-10-15  2:30 ` patchwork-bot+netdevbpf [this message]
2021-10-15  2:30   ` patchwork-bot+netdevbpf

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=163426500848.31820.18368368881396978501.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=davem@davemloft.net \
    --cc=jdike@addtoit.com \
    --cc=kuba@kernel.org \
    --cc=linux-um@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=richard@nod.at \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.