All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Mengyuan Lou <mengyuanlou@net-swift.com>
Cc: netdev@vger.kernel.org, jiawenwu@trustnetic.com,
	duanqiangwen@net-swift.com
Subject: Re: [PATCH net-next v3 0/6] add sriov support for wangxun NICs
Date: Wed, 15 May 2024 16:31:31 +0100	[thread overview]
Message-ID: <20240515153131.GP154012@kernel.org> (raw)
In-Reply-To: <A621A96B7D9B15C2+20240515100830.32920-1-mengyuanlou@net-swift.com>

On Wed, May 15, 2024 at 05:50:03PM +0800, Mengyuan Lou wrote:
> Add sriov_configure for ngbe and txgbe drivers.
> Reallocate queue and irq resources when sriov is enabled.
> Add wx_msg_task in interrupts handler, which is used to process the
> configuration sent by vfs.
> Add ping_vf for wx_pf to tell vfs about pf link change.

Hi Mengyuan Lou,

Thanks for your updated patch-set.

Unfortunately net-next is currently closed for the v6.10 merge window.
Please consider reposting as a PATCH once net-next re-opens, after 27th May.

In the meantime, feel free to post new versions as you get feedback,
but please switch to posting as RFC during that time.

Link: https://docs.kernel.org/process/maintainer-netdev.html

Also, please be sure to seed the CC list of your patch submissions
using the output of get-maintainers.pl PATCH. b4 can also be of
assistance here.

  reply	other threads:[~2024-05-15 15:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15  9:50 [PATCH net-next v3 0/6] add sriov support for wangxun NICs Mengyuan Lou
2024-05-15 15:31 ` Simon Horman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-15 10:54 Mengyuan Lou
2024-04-15 18:27 ` Jakub Kicinski
2024-04-16  2:55   ` mengyuanlou
2024-04-16 14:31     ` Jakub Kicinski
2024-05-14 10:24       ` mengyuanlou

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=20240515153131.GP154012@kernel.org \
    --to=horms@kernel.org \
    --cc=duanqiangwen@net-swift.com \
    --cc=jiawenwu@trustnetic.com \
    --cc=mengyuanlou@net-swift.com \
    --cc=netdev@vger.kernel.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 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.