From: Jacob Keller <jacob.e.keller@intel.com>
To: Parav Pandit <parav@mellanox.com>, netdev@vger.kernel.org
Cc: stephen@networkplumber.org, dsahern@kernel.org, jiri@mellanox.com
Subject: Re: [PATCH net-next iproute2 1/2] Update devlink kernel header
Date: Thu, 5 Mar 2020 16:42:59 -0800 [thread overview]
Message-ID: <bfef88f7-c888-04b0-7d7d-dc1bb184d168@intel.com> (raw)
In-Reply-To: <20200304040626.26320-2-parav@mellanox.com>
On 3/3/2020 8:06 PM, Parav Pandit wrote:
> Update devlink kernel header to commit:
> acf1ee44ca5d ("devlink: Introduce devlink port flavour virtual")
>
> Signed-off-by: Parav Pandit <parav@mellanox.com>
> ---
> include/uapi/linux/devlink.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/include/uapi/linux/devlink.h b/include/uapi/linux/devlink.h
> index 3f82dedd..1b412281 100644
> --- a/include/uapi/linux/devlink.h
> +++ b/include/uapi/linux/devlink.h
> @@ -187,6 +187,7 @@ enum devlink_port_flavour {
> * for the PCI VF. It is an internal
> * port that faces the PCI VF.
> */
> + DEVLINK_PORT_FLAVOUR_VIRTUAL, /* Any virtual port facing the user. */
> };
>
> enum devlink_param_cmode {
> @@ -252,6 +253,8 @@ enum devlink_trap_type {
> enum {
> /* Trap can report input port as metadata */
> DEVLINK_ATTR_TRAP_METADATA_TYPE_IN_PORT,
> + /* Trap can report flow action cookie as metadata */
> + DEVLINK_ATTR_TRAP_METADATA_TYPE_FA_COOKIE,
> };
>
This hunk doesn't seem relevant to the patch and isn't mentioned in the
subject or description.
Thanks,
Jake
> enum devlink_attr {
>
next prev parent reply other threads:[~2020-03-06 0:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 4:06 [PATCH net-next iproute2 0/2] devlink: Introduce devlink port flavour virtual Parav Pandit
2020-03-04 4:06 ` [PATCH net-next iproute2 1/2] Update devlink kernel header Parav Pandit
2020-03-06 0:42 ` Jacob Keller [this message]
2020-03-06 0:43 ` David Ahern
2020-03-06 0:55 ` Jacob Keller
2020-03-06 0:44 ` Jacob Keller
2020-03-04 4:06 ` [PATCH net-next iproute2 2/2] devlink: Introduce devlink port flavour virtual Parav Pandit
2020-03-04 19:48 ` David Ahern
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=bfef88f7-c888-04b0-7d7d-dc1bb184d168@intel.com \
--to=jacob.e.keller@intel.com \
--cc=dsahern@kernel.org \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=parav@mellanox.com \
--cc=stephen@networkplumber.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).