All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Martin Habets <habetsm.xilinx@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, jonathan.s.cooper@amd.com,
	netdev@vger.kernel.org, ecree.xilinx@gmail.com
Subject: Re: [PATCH net-next v2 00/10]  sfc: Add extra states for VDPA
Date: Wed, 29 Jun 2022 12:50:20 +0000	[thread overview]
Message-ID: <165650702021.9231.8524288962828359852.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <165642465886.31669.17429834766693417246.stgit@palantir17.mph.net>

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Tue, 28 Jun 2022 14:58:43 +0100 you wrote:
> For EF100 VDPA support we need to enhance the sfc driver's load and
> unload functionality so that it can probe and then unregister its
> network device, so that VDPA can use services such as MCDI to initialise
> VDPA resources.
> 
> v2:
> - Fix checkpatch errors.
> - Correct signoffs.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,01/10] sfc: Split STATE_READY in to STATE_NET_DOWN and STATE_NET_UP.
    https://git.kernel.org/netdev/net-next/c/813cf9d1e753
  - [net-next,v2,02/10] sfc: Add a PROBED state for EF100 VDPA use.
    https://git.kernel.org/netdev/net-next/c/8b39db19b21b
  - [net-next,v2,03/10] sfc: Remove netdev init from efx_init_struct
    https://git.kernel.org/netdev/net-next/c/62ac3ce542ff
  - [net-next,v2,04/10] sfc: Change BUG_ON to WARN_ON and recovery code.
    https://git.kernel.org/netdev/net-next/c/b3fd0a86dad2
  - [net-next,v2,05/10] sfc: Encapsulate access to netdev_priv()
    https://git.kernel.org/netdev/net-next/c/8cb03f4e084e
  - [net-next,v2,06/10] sfc: Separate efx_nic memory from net_device memory
    https://git.kernel.org/netdev/net-next/c/7e773594dada
  - [net-next,v2,07/10] sfc: Move EF100 efx_nic_type structs to the end of the file
    https://git.kernel.org/netdev/net-next/c/3e341d84bd9f
  - [net-next,v2,08/10] sfc: Unsplit literal string.
    https://git.kernel.org/netdev/net-next/c/bba84bf4c1f2
  - [net-next,v2,09/10] sfc: replace function name in string with __func__
    https://git.kernel.org/netdev/net-next/c/7592d754c09c
  - [net-next,v2,10/10] sfc: Separate netdev probe/remove from PCI probe/remove
    https://git.kernel.org/netdev/net-next/c/98ff4c7c8ac7

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



      parent reply	other threads:[~2022-06-29 12:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 13:58 [PATCH net-next v2 00/10] sfc: Add extra states for VDPA Martin Habets
2022-06-28 13:58 ` [PATCH net-next v2 01/10] sfc: Split STATE_READY in to STATE_NET_DOWN and STATE_NET_UP Martin Habets
2022-06-28 13:59 ` [PATCH net-next v2 02/10] sfc: Add a PROBED state for EF100 VDPA use Martin Habets
2022-06-28 13:59 ` [PATCH net-next v2 03/10] sfc: Remove netdev init from efx_init_struct Martin Habets
2022-06-28 13:59 ` [PATCH net-next v2 04/10] sfc: Change BUG_ON to WARN_ON and recovery code Martin Habets
2022-06-28 13:59 ` [PATCH net-next v2 05/10] sfc: Encapsulate access to netdev_priv() Martin Habets
2022-06-28 13:59 ` [PATCH net-next v2 06/10] sfc: Separate efx_nic memory from net_device memory Martin Habets
2022-06-28 14:00 ` [PATCH net-next v2 07/10] sfc: Move EF100 efx_nic_type structs to the end of the file Martin Habets
2022-06-28 14:00 ` [PATCH net-next v2 08/10] sfc: Unsplit literal string Martin Habets
2022-06-28 14:00 ` [PATCH net-next v2 09/10] sfc: replace function name in string with __func__ Martin Habets
2022-06-28 14:00 ` [PATCH net-next v2 10/10] sfc: Separate netdev probe/remove from PCI probe/remove Martin Habets
2022-06-29 12:50 ` 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=165650702021.9231.8524288962828359852.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=habetsm.xilinx@gmail.com \
    --cc=jonathan.s.cooper@amd.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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.