public inbox for linux-kernel-mentees@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: swarup <swarupkotikalapudi@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, jiri@resnulli.us, netdev@vger.kernel.org,
	linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH net-next v6] netlink: specs: devlink: add some(not all) missing attributes in devlink.yaml
Date: Tue, 12 Dec 2023 03:20:25 +0000	[thread overview]
Message-ID: <170235122572.10568.5224501495681522792.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231208182515.1206616-1-swarupkotikalapudi@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri,  8 Dec 2023 23:55:15 +0530 you wrote:
> Add some missing(not all) attributes in devlink.yaml.
> 
> Signed-off-by: Swarup Laxman Kotiaklapudi <swarupkotikalapudi@gmail.com>
> Suggested-by: Jiri Pirko <jiri@resnulli.us>
> ---
> V6:
>   - Fix review comments
> V5:
>   - https://lore.kernel.org/all/20231202123048.1059412-1-swarupkotikalapudi@gmail.com/
>     Keep stats enum as unnamed in /uapi/linux/devlink.h
>     to avoid kernel build failure
> V4: https://lore.kernel.org/all/20231126105246.195288-1-swarupkotikalapudi@gmail.com/
>   - Change the commit message
> V3: https://lore.kernel.org/all/20231123100119.148324-1-swarupkotikalapudi@gmail.com/
>   - enum name added for stats and trap-metadata enum used by trap command
>     in include/uapi/linux/devlink.h
>   - Fix generated userspace file's compilation issue
>     due to V1 and V2 patchset
>   - Move some attributes e.g. nested-devlink and param again as a TODO,
>     which needs some discussion and will be fixed in a new patchset
> V2: https://lore.kernel.org/all/20231122143033.89856-1-swarupkotikalapudi@gmail.com/
>   - Rebase to net-next tree
>   - param-value-data data type is dynamic, hence to accomndate
>     all data type make it as string type
>   - Change nested attribute to use correct fields
>     based on driver code e.g. region-snapshots,
>     region-snapshot, region-chunks, region-chunk,
>     linecard-supported-types, health-reporter,
>     linecard-supported-types, nested-devlink
>     and param's attributes
> V1: https://lore.kernel.org/all/ZVNPi7pmJIDJ6Ms7@swarup-virtual-machine/
> 
> [...]

Here is the summary with links:
  - [net-next,v6] netlink: specs: devlink: add some(not all) missing attributes in devlink.yaml
    https://git.kernel.org/netdev/net-next/c/68c84289bcc0

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



      parent reply	other threads:[~2023-12-12  3:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 18:25 [PATCH net-next v6] netlink: specs: devlink: add some(not all) missing attributes in devlink.yaml Swarup Laxman Kotiaklapudi
2023-12-11  9:46 ` Jiri Pirko
2023-12-11 12:20   ` swarup
2023-12-11 12:35     ` Jiri Pirko
2023-12-12  3:20 ` 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=170235122572.10568.5224501495681522792.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=swarupkotikalapudi@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox