From: Jakub Kicinski <kuba@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
donald.hunter@gmail.com, ast@fiberby.net
Subject: Re: [PATCH net-next v2 2/2] tools: ynl: rework the string representation of NlError
Date: Tue, 28 Oct 2025 16:34:54 -0700 [thread overview]
Message-ID: <20251028163454.66ca7dc3@kernel.org> (raw)
In-Reply-To: <53ad4e54-47c7-4afa-a296-635e10192f8c@lunn.ch>
On Tue, 28 Oct 2025 14:58:59 +0100 Andrew Lunn wrote:
> I think as a kernel programmer, i would prefer EINVAL over Invalid
> argument. If i'm going to be digging into the kernel sources to find
> where the error is happening, it is one less translation i need to
> make.
>
> >>> print(errno.errorcode[1])
> EPERM
> >>> print(errno.errorcode[2])
> ENOENT
> >>> print(errno.errorcode[110])
> ETIMEDOUT
>
> I suppose the question is, who is the intended user of ynl? Do we want
> user friendly messages, or kernel developer friendly messages?
A mix of both, it is packaged in distros.
next prev parent reply other threads:[~2025-10-28 23:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 19:29 [PATCH net-next v2 1/2] tools: ynl: fix indent issues in the main Python lib Jakub Kicinski
2025-10-27 19:29 ` [PATCH net-next v2 2/2] tools: ynl: rework the string representation of NlError Jakub Kicinski
2025-10-28 10:51 ` Donald Hunter
2025-10-28 13:58 ` Andrew Lunn
2025-10-28 23:34 ` Jakub Kicinski [this message]
2025-10-28 10:50 ` [PATCH net-next v2 1/2] tools: ynl: fix indent issues in the main Python lib Donald Hunter
2025-10-28 23:50 ` 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=20251028163454.66ca7dc3@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=ast@fiberby.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@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.