From: keith.busch@linux.intel.com (Keith Busch)
Subject: Read request exceeding max_hw_sectors_kb
Date: Tue, 26 Jun 2018 09:07:00 -0600 [thread overview]
Message-ID: <20180626150700.GC6628@localhost.localdomain> (raw)
In-Reply-To: <719bd24e00a4f9ed70b9d17472febf24@mail.gmail.com>
On Tue, Jun 26, 2018@04:17:35PM +0530, Jitendra Bhivare wrote:
> Sorry for the delayed response. This patch works fine too. Please submit
> it.
Will do, thanks for the confirmation. Okay if I add your Tested-by?
WARNING: multiple messages have this Message-ID (diff)
From: Keith Busch <keith.busch at linux.intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Read request exceeding max_hw_sectors_kb
Date: Tue, 26 Jun 2018 09:07:00 -0600 [thread overview]
Message-ID: <20180626150700.GC6628@localhost.localdomain> (raw)
In-Reply-To: 719bd24e00a4f9ed70b9d17472febf24@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 222 bytes --]
On Tue, Jun 26, 2018 at 04:17:35PM +0530, Jitendra Bhivare wrote:
> Sorry for the delayed response. This patch works fine too. Please submit
> it.
Will do, thanks for the confirmation. Okay if I add your Tested-by?
next prev parent reply other threads:[~2018-06-26 15:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 10:41 Read request exceeding max_hw_sectors_kb Jitendra Bhivare
2018-06-13 10:41 ` [SPDK] " Jitendra Bhivare
2018-06-13 11:47 ` Christoph Hellwig
2018-06-13 11:47 ` [SPDK] " Christoph Hellwig
2018-06-13 17:00 ` Daniel Verkamp
2018-06-13 17:00 ` [SPDK] " Daniel Verkamp
2018-06-14 10:16 ` Jitendra Bhivare
2018-06-14 10:16 ` [SPDK] " Jitendra Bhivare
2018-06-14 14:54 ` Keith Busch
2018-06-14 14:54 ` [SPDK] " Keith Busch
2018-06-15 13:58 ` Jitendra Bhivare
2018-06-15 13:58 ` [SPDK] " Jitendra Bhivare
2018-06-26 10:47 ` Jitendra Bhivare
2018-06-26 10:47 ` [SPDK] " Jitendra Bhivare
2018-06-26 15:07 ` Keith Busch [this message]
2018-06-26 15:07 ` Keith Busch
2018-06-27 10:28 ` Jitendra Bhivare
2018-06-27 10:28 ` [SPDK] " Jitendra Bhivare
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=20180626150700.GC6628@localhost.localdomain \
--to=keith.busch@linux.intel.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 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.