netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: mengyuanlou <mengyuanlou@net-swift.com>
Cc: netdev@vger.kernel.org, jiawenwu@trustnetic.com,
	duanqiangwen@net-swift.com
Subject: Re: [PATCH net-next v7 4/6] net: libwx: Add msg task func
Date: Fri, 7 Feb 2025 17:17:39 -0800	[thread overview]
Message-ID: <20250207171739.7ab11585@kernel.org> (raw)
In-Reply-To: <20250206103750.36064-5-mengyuanlou@net-swift.com>

On Thu,  6 Feb 2025 18:37:48 +0800 mengyuanlou wrote:
> +static int wx_negotiate_vf_api(struct wx *wx, u32 *msgbuf, u32 vf)
> +{
> +	int api = msgbuf[1];
> +
> +	switch (api) {
> +	case wx_mbox_api_10 ... wx_mbox_api_13:
> +		wx->vfinfo[vf].vf_api = api;
> +		return 0;
> +	default:
> +		wx_err(wx, "VF %d requested invalid api version %u\n", vf, api);
> +		return -EINVAL;
> +	}
> +}

How "compatible" is your device with IXGBE?

static int ixgbe_negotiate_vf_api(struct ixgbe_adapter *adapter,                
                                  u32 *msgbuf, u32 vf)                          
{                                                                               
        int api = msgbuf[1];                                                    
                                                                                
        switch (api) {                                                          
        case ixgbe_mbox_api_10:                                                 
        case ixgbe_mbox_api_11:                                                 
        case ixgbe_mbox_api_12:                                                 
        case ixgbe_mbox_api_13:                                                 
        case ixgbe_mbox_api_14:                                                 
                adapter->vfinfo[vf].vf_api = api;                               
                return 0;                                                       
        default:                                                                
                break;                                                          
        }                                                                       
                                                                                
        e_dbg(drv, "VF %d requested unsupported api version %u\n", vf, api);    
                                                                                
        return -1;                                                              
}                                                                               

  reply	other threads:[~2025-02-08  1:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 10:37 [PATCH net-next v7 0/6] add sriov support for wangxun NICs mengyuanlou
2025-02-06 10:37 ` [PATCH net-next v7 1/6] net: libwx: Add malibox api for wangxun pf drivers mengyuanlou
2025-02-06 10:37 ` [PATCH net-next v7 2/6] net: libwx: Add sriov api for wangxun nics mengyuanlou
2025-02-08  1:12   ` Jakub Kicinski
2025-02-06 10:37 ` [PATCH net-next v7 3/6] net: libwx: Redesign flow when sriov is enabled mengyuanlou
2025-02-08  1:15   ` Jakub Kicinski
2025-02-11 11:17     ` mengyuanlou
2025-02-06 10:37 ` [PATCH net-next v7 4/6] net: libwx: Add msg task func mengyuanlou
2025-02-08  1:17   ` Jakub Kicinski [this message]
2025-02-11 11:14     ` mengyuanlou
2025-02-06 10:37 ` [PATCH net-next v7 5/6] net: ngbe: add sriov function support mengyuanlou
2025-02-08  1:19   ` Jakub Kicinski
2025-02-11 11:14     ` mengyuanlou
2025-02-11 22:06       ` Jakub Kicinski
2025-02-12 11:06         ` mengyuanlou
2025-02-13  2:09           ` Jakub Kicinski
2025-02-06 10:37 ` [PATCH net-next v7 6/6] net: txgbe: " mengyuanlou
2025-02-08  1:09   ` Jakub Kicinski

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=20250207171739.7ab11585@kernel.org \
    --to=kuba@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).