From: Jakub Kicinski <kuba@kernel.org>
To: Haofeng Li <920484857@qq.com>
Cc: Donald Hunter <donald.hunter@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Haofeng Li <13266079573@163.com>,
Haofeng Li <lihaofeng@kylinos.cn>
Subject: Re: [PATCH] net: ynl: return actual error code in ynl_exec_dump()
Date: Fri, 26 Sep 2025 11:24:06 -0700 [thread overview]
Message-ID: <20250926112406.1d92c89d@kernel.org> (raw)
In-Reply-To: <tencent_16B08FED03C970A0B8F75F16AE3D7A2F3305@qq.com>
On Fri, 26 Sep 2025 17:58:20 +0800 Haofeng Li wrote:
> Return the real error code 'err' instead of hardcoded -1 in the error
> path of ynl_exec_dump(). This provides better error information to
> callers for debugging and error handling.
Do you have a realistic example that can happen today? This is not
kernel code the error is always -1, and the details are in errno.
next prev parent reply other threads:[~2025-09-26 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 9:58 [PATCH] net: ynl: return actual error code in ynl_exec_dump() Haofeng Li
2025-09-26 18:24 ` Jakub Kicinski [this message]
2025-09-30 12:39 ` [PATCH WITHDRAWN] " Haofeng Li
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=20250926112406.1d92c89d@kernel.org \
--to=kuba@kernel.org \
--cc=13266079573@163.com \
--cc=920484857@qq.com \
--cc=donald.hunter@gmail.com \
--cc=lihaofeng@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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 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.