From: Martin Wilck <mwilck@suse.com>
To: Guan Junxiong <guanjunxiong@huawei.com>
Cc: "dm-devel@redhat.com" <dm-devel@redhat.com>,
niuhaoxin <niuhaoxin@huawei.com>,
"Shenhong (C)" <shenhong09@huawei.com>
Subject: Re: [PATCH 3/4] libmultipath: path latency: simplify getprio()
Date: Thu, 23 Nov 2017 13:23:13 +0100 [thread overview]
Message-ID: <1511439793.1655.37.camel@suse.com> (raw)
In-Reply-To: <ee0117c2-502f-d211-f55e-20a23c98874a@huawei.com>
On Thu, 2017-11-23 at 10:20 +0800, Guan Junxiong wrote:
> Hi Martin，
>
> Thanks for your clarification. I agree with you now in this thread.
Thank you. I'd be grateful if you could give these patches a test in
your environment, I believe you have better testing equipment for this
stuff than I do.
Just in case I made a silly mistake.
Martin
--
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2017-11-23 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <06F84A57D601574CAA706EE1A6270A5F01039500@DGGEMM505-MBX.china.huawei.com>
2017-11-23 2:20 ` [PATCH 3/4] libmultipath: path latency: simplify getprio() Guan Junxiong
2017-11-23 12:23 ` Martin Wilck [this message]
2017-11-18 0:11 [PATCH 0/4] path latency prio fixes Martin Wilck
2017-11-18 0:11 ` [PATCH 3/4] libmultipath: path latency: simplify getprio() Martin Wilck
2017-11-19 2:52 ` Guan Junxiong
2017-11-20 8:46 ` Martin Wilck
2017-12-07 4:26 ` Guan Junxiong
2017-12-07 15:56 ` Martin Wilck
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=1511439793.1655.37.camel@suse.com \
--to=mwilck@suse.com \
--cc=dm-devel@redhat.com \
--cc=guanjunxiong@huawei.com \
--cc=niuhaoxin@huawei.com \
--cc=shenhong09@huawei.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