All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Peter Morrow <pdmorrow@gmail.com>
Cc: tariqt@nvidia.com, leon@kernel.org, petr.pavlu@suse.com,
	yishaih@nvidia.com, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, andrew+netdev@lunn.ch, davem@davemloft.net,
	netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	regressions@lists.linux.dev
Subject: Re: [PATCH net] net/mlx4: always create the eth and ib auxiliary devices
Date: Wed, 28 Oct 2026 08:40:23 +0000	[thread overview]
Message-ID: <179317682332.583220.822272904304785815.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261020164239.3808903-1-pdmorrow@gmail.com>

Hello:

This patch was applied to netdev/net.git (main)
by Dave Miller <davem@davem-thinkpadp1gen8.ibmlond.csb>:

On Tue, 20 Oct 2026 17:42:39 +0100 you wrote:
> Since commit 7d22b1cb9d84 ("mlx4: Connect the infiniband part to the
> auxiliary bus"), mlx4_core creates the "ib" auxiliary device only for
> an IB port or a device that advertises IBoE. Before it, each mlx4
> interface was offered every device and decided in its own add callback.
> mlx4_ib_add() accepted Ethernet ports without IBoE and registered them
> for raw packet QPs only.
> 
> [...]

Here is the summary with links:
  - [net] net/mlx4: always create the eth and ib auxiliary devices
    https://git.kernel.org/netdev/net/c/557d80138618

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



      parent reply	other threads:[~2026-10-28  8:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 16:42 [PATCH net] net/mlx4: always create the eth and ib auxiliary devices Peter Morrow
2026-10-20 16:48 ` sashiko-bot
2026-10-22 10:19 ` Simon Horman
2026-10-23 14:08   ` Peter Morrow
2026-10-23 16:56     ` Simon Horman
2026-10-23 11:22 ` Daniel Machon
2026-10-27  8:50 ` Paolo Abeni
2026-10-28  7:20 ` Tariq Toukan
2026-10-28  8:40 ` 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=179317682332.583220.822272904304785815.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pdmorrow@gmail.com \
    --cc=petr.pavlu@suse.com \
    --cc=regressions@lists.linux.dev \
    --cc=tariqt@nvidia.com \
    --cc=yishaih@nvidia.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 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.