From: Jiri Pirko <jiri@resnulli.us>
To: David Ahern <dsahern@gmail.com>
Cc: netdev@vger.kernel.org, stephen@networkplumber.org,
mlxsw@mellanox.com, valex@mellanox.com
Subject: Re: [patch iproute2-next] man: fix devlink object list
Date: Mon, 2 Apr 2018 11:15:37 +0200 [thread overview]
Message-ID: <20180402091537.GF3313@nanopsycho> (raw)
In-Reply-To: <1ce8129e-444f-8424-5db2-e6761090bf60@gmail.com>
Fri, Mar 30, 2018 at 06:43:33PM CEST, dsahern@gmail.com wrote:
>On 3/29/18 8:26 AM, Jiri Pirko wrote:
>> From: Jiri Pirko <jiri@mellanox.com>
>>
>> Signed-off-by: Jiri Pirko <jiri@mellanox.com>
>> ---
>> man/man8/devlink.8 | 10 +++++++++-
>> 1 file changed, 9 insertions(+), 1 deletion(-)
>>
>
>resource and sb exist on master, so this patch seems more appropriate
>for it than -next.
It's a documentation fix, so I sent it to -next. I don't mind this to be
applied on master though. Stephen?
prev parent reply other threads:[~2018-04-02 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 14:26 [patch iproute2-next] man: fix devlink object list Jiri Pirko
2018-03-30 16:43 ` David Ahern
2018-04-02 9:15 ` Jiri Pirko [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=20180402091537.GF3313@nanopsycho \
--to=jiri@resnulli.us \
--cc=dsahern@gmail.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=valex@mellanox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox