From: Aya Levin <ayal@mellanox.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
Tariq Toukan <tariqt@mellanox.com>
Cc: David Ahern <dsahern@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Moshe Shemesh <moshe@mellanox.com>,
Jiri Pirko <jiri@mellanox.com>
Subject: Re: [PATCH iproute2 4/4] devlink: Fix devlink health set command
Date: Wed, 18 Sep 2019 07:07:55 +0000 [thread overview]
Message-ID: <3052d758-4c3c-7b07-7fa2-e46c45210719@mellanox.com> (raw)
In-Reply-To: <20190917172357.5c70c3b9@xps13.home>
On 9/17/2019 6:23 PM, Stephen Hemminger wrote:
> On Thu, 5 Sep 2019 15:43:07 +0300
> Tariq Toukan <tariqt@mellanox.com> wrote:
>
>> From: Aya Levin <ayal@mellanox.com>
>>
>> Prior to this patch both the reporter's name and the grace period
>> attributes shared the same bit. This caused zeroing grace period when
>> setting auto recovery. Let each parameter has its own bit.
>>
>> Fixes: b18d89195b16 ("devlink: Add devlink health set command")
>> Signed-off-by: Aya Levin <ayal@mellanox.com>
>> Acked-by: Jiri Pirko <jiri@mellanox.com>
>> Signed-off-by: Tariq Toukan <tariqt@mellanox.com>
>
> Does not apply to current iproute2.
This patch is redundant due to patch from Andrea Claudi
4fb98f08956ff4810354d75afa9b04cb6f8011bc
Please reject it.
Other patches that were submitted with, are valid.
>
prev parent reply other threads:[~2019-09-18 7:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 12:43 [PATCH iproute2 0/4] Devlink health FMSG fixes and enhancements Tariq Toukan
2019-09-05 12:43 ` [PATCH iproute2 1/4] devlink: Add helper for left justification print Tariq Toukan
2019-09-05 12:43 ` [PATCH iproute2 2/4] devlink: Left justification on FMSG output Tariq Toukan
2019-09-05 12:43 ` [PATCH iproute2 3/4] devlink: Fix inconsistency between command input and output Tariq Toukan
2019-09-05 12:43 ` [PATCH iproute2 4/4] devlink: Fix devlink health set command Tariq Toukan
2019-09-17 15:23 ` Stephen Hemminger
2019-09-18 7:07 ` Aya Levin [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=3052d758-4c3c-7b07-7fa2-e46c45210719@mellanox.com \
--to=ayal@mellanox.com \
--cc=dsahern@gmail.com \
--cc=jiri@mellanox.com \
--cc=moshe@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=tariqt@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