All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, lorenzo@kernel.org
Subject: Re: [PATCH net 0/2] tools: ynl: fix enum-as-flags in the generic CLI
Date: Thu, 09 Mar 2023 07:30:19 +0000	[thread overview]
Message-ID: <167834701930.22182.11614438480026068450.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230308003923.445268-1-kuba@kernel.org>

Hello:

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

On Tue,  7 Mar 2023 16:39:21 -0800 you wrote:
> The CLI needs to use proper classes when looking at Enum definitions
> rather than interpreting the YAML spec ad-hoc, because we have more
> than on format of the definition supported.
> 
> Jakub Kicinski (2):
>   tools: ynl: move the enum classes to shared code
>   tools: ynl: fix enum-as-flags in the generic CLI
> 
> [...]

Here is the summary with links:
  - [net,1/2] tools: ynl: move the enum classes to shared code
    https://git.kernel.org/netdev/net/c/6517a60b0307
  - [net,2/2] tools: ynl: fix enum-as-flags in the generic CLI
    https://git.kernel.org/netdev/net/c/c311aaa74ca1

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-03-09  7:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08  0:39 [PATCH net 0/2] tools: ynl: fix enum-as-flags in the generic CLI Jakub Kicinski
2023-03-08  0:39 ` [PATCH net 1/2] tools: ynl: move the enum classes to shared code Jakub Kicinski
2023-03-08  0:39 ` [PATCH net 2/2] tools: ynl: fix enum-as-flags in the generic CLI Jakub Kicinski
2023-03-09  7:30 ` 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=167834701930.22182.11614438480026068450.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=lorenzo@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.