From: Petr Machata <petrm@nvidia.com>
To: David Ahern <dsahern@gmail.com>
Cc: Petr Machata <petrm@nvidia.com>, <netdev@vger.kernel.org>,
<stephen@networkplumber.org>, Ido Schimmel <idosch@nvidia.com>,
Petr Machata <me@pmachata.org>
Subject: Re: [PATCH iproute2-next 4/6] nexthop: Add ability to specify group type
Date: Mon, 15 Mar 2021 12:38:15 +0100 [thread overview]
Message-ID: <87zgz4hck9.fsf@nvidia.com> (raw)
In-Reply-To: <5397a5b8-da46-7290-9395-5fcd46121f42@gmail.com>
David Ahern <dsahern@gmail.com> writes:
> On 3/12/21 10:23 AM, Petr Machata wrote:
>> From: Petr Machata <me@pmachata.org>
>>
>> From: Ido Schimmel <idosch@nvidia.com>
>
> All of the patches have the above. If Ido is the author and you are
> sending, AIUI you add your Signed-off-by below his.
Sorry about that, that's a leftover from when I was sending the DCB
patches. I'll resend with the correct headers.
>> +.sp
>> +.I TYPE
>> +is a string specifying the nexthop group type. Namely:
>> +
>> +.in +8
>> +.BI mpath
>> +- multipath nexthop group
>> +
>
> Add a comment that this is the default group type and refers to the
> legacy hash-bashed multipath group.
OK.
next prev parent reply other threads:[~2021-03-15 11:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 17:23 [PATCH iproute2-next 0/6] ip: nexthop: Support resilient groups Petr Machata
2021-03-12 17:23 ` [PATCH iproute2-next 1/6] nexthop: Synchronize uAPI files Petr Machata
2021-03-12 17:23 ` [PATCH iproute2-next 2/6] json_print: Add print_tv() Petr Machata
2021-03-12 17:23 ` [PATCH iproute2-next 3/6] nexthop: Extract a helper to parse a NH ID Petr Machata
2021-03-12 17:23 ` [PATCH iproute2-next 4/6] nexthop: Add ability to specify group type Petr Machata
2021-03-14 15:55 ` David Ahern
2021-03-15 11:38 ` Petr Machata [this message]
2021-03-12 17:23 ` [PATCH iproute2-next 5/6] nexthop: Add support for resilient nexthop groups Petr Machata
2021-03-12 17:23 ` [PATCH iproute2-next 6/6] nexthop: Add support for nexthop buckets Petr Machata
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=87zgz4hck9.fsf@nvidia.com \
--to=petrm@nvidia.com \
--cc=dsahern@gmail.com \
--cc=idosch@nvidia.com \
--cc=me@pmachata.org \
--cc=netdev@vger.kernel.org \
--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 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.