From: Sagi Grimberg <sagi@grimberg.me>
To: Tony Asleson <tasleson@redhat.com>, linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvmetcli: Correct xrange usage for py3
Date: Wed, 1 Apr 2020 13:35:11 -0700 [thread overview]
Message-ID: <3ddf95f2-5f4e-21b1-e8d1-fac8e7af195b@grimberg.me> (raw)
In-Reply-To: <20200401191316.54355-1-tasleson@redhat.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-04-01 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 19:13 [PATCH] nvmetcli: Correct xrange usage for py3 Tony Asleson
2020-04-01 20:35 ` Sagi Grimberg [this message]
2020-04-03 6:55 ` Christoph Hellwig
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=3ddf95f2-5f4e-21b1-e8d1-fac8e7af195b@grimberg.me \
--to=sagi@grimberg.me \
--cc=linux-nvme@lists.infradead.org \
--cc=tasleson@redhat.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