From: Jakub Kicinski <kuba@kernel.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, saeedm@nvidia.com, horms@kernel.org,
donald.hunter@gmail.com
Subject: Re: [PATCH net-next v2 1/4] tools: ynl-gen: allow noncontiguous enums
Date: Tue, 6 May 2025 18:22:25 -0700 [thread overview]
Message-ID: <20250506182225.531a036e@kernel.org> (raw)
In-Reply-To: <5mgfrsapfnljlminy67o2wnz3iwh3mqba7fazt4ku2v6xh5t4g@nwgn3rdndvng>
On Tue, 6 May 2025 08:38:36 +0200 Jiri Pirko wrote:
> Mon, May 05, 2025 at 01:45:10PM +0200, jiri@resnulli.us wrote:
> >From: Jiri Pirko <jiri@nvidia.com>
> >
> >in case the enum has holes, instead of hard stop, generate a validation
> >callback to check valid enum values.
> >
> >signed-off-by: jiri pirko <jiri@nvidia.com>
>
> By some accident I managed to remove uppercases from this line. Should I
> repost or would you fix this during apply in case there are no changes
> requested?
No worries, I don't think it's a big deal as long as the email matches.
But I'll fix when applying.
next prev parent reply other threads:[~2025-05-07 1:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 11:45 [PATCH net-next v2 0/4] devlink: sanitize variable typed attributes Jiri Pirko
2025-05-05 11:45 ` [PATCH net-next v2 1/4] tools: ynl-gen: allow noncontiguous enums Jiri Pirko
2025-05-06 6:38 ` Jiri Pirko
2025-05-07 1:22 ` Jakub Kicinski [this message]
2025-05-05 11:45 ` [PATCH net-next v2 2/4] devlink: define enum for attr types of dynamic attributes Jiri Pirko
2025-05-05 11:45 ` [PATCH net-next v2 3/4] devlink: avoid param type value translations Jiri Pirko
2025-05-05 11:45 ` [PATCH net-next v2 4/4] devlink: use DEVLINK_VAR_ATTR_TYPE_* instead of NLA_* in fmsg Jiri Pirko
2025-05-07 1:30 ` [PATCH net-next v2 0/4] devlink: sanitize variable typed attributes patchwork-bot+netdevbpf
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=20250506182225.531a036e@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.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.