From: David Ahern <dsahern@gmail.com>
To: Parav Pandit <parav@nvidia.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: Jiri Pirko <jiri@nvidia.com>
Subject: Re: [PATCH RESEND iproute2-next] devlink: Add optional controller user input
Date: Mon, 7 Jun 2021 09:15:47 -0600 [thread overview]
Message-ID: <531cec55-d460-3254-df23-4adac5c18743@gmail.com> (raw)
In-Reply-To: <PH0PR12MB54813150C3567170590BE36DDC389@PH0PR12MB5481.namprd12.prod.outlook.com>
On 6/7/21 9:12 AM, Parav Pandit wrote:
> I see. So do you recommend splitting the print message?
> I personally feel easier to follow kernel coding standard as much possible in spirit of "grep them". 😊
> But its really up to you. Please let me know.
yes, I am saying user help messages from commands are different than
kernel code. Users are not typically grepping iproute2 source code
looking up the help string.
next prev parent reply other threads:[~2021-06-07 15:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 11:19 [PATCH RESEND iproute2-next] devlink: Add optional controller user input Parav Pandit
2021-06-04 1:34 ` Yunsheng Lin
2021-06-06 7:10 ` Parav Pandit
2021-06-07 3:31 ` Yunsheng Lin
2021-06-07 6:10 ` Parav Pandit
2021-06-07 10:56 ` Yunsheng Lin
2021-06-07 11:12 ` Parav Pandit
2021-06-08 3:27 ` Yunsheng Lin
2021-06-08 5:26 ` Parav Pandit
2021-06-08 7:35 ` Yunsheng Lin
2021-06-08 8:47 ` Parav Pandit
2021-06-08 9:32 ` Yunsheng Lin
2021-06-09 9:24 ` Parav Pandit
2021-06-09 11:35 ` Yunsheng Lin
2021-06-09 11:41 ` Parav Pandit
2021-06-07 3:00 ` David Ahern
2021-06-07 11:43 ` Parav Pandit
2021-06-07 14:41 ` David Ahern
2021-06-07 15:12 ` Parav Pandit
2021-06-07 15:15 ` David Ahern [this message]
2021-06-07 16:14 ` David Ahern
2021-06-07 18:26 ` Parav Pandit
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=531cec55-d460-3254-df23-4adac5c18743@gmail.com \
--to=dsahern@gmail.com \
--cc=jiri@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=stephen@networkplumber.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).