From: Jens Axboe <axboe@kernel.dk>
To: Omar Sandoval <osandov@osandov.com>, linux-block@vger.kernel.org
Cc: linux-nvme@lists.infradead.org, linux-scsi@vger.kernel.org,
kernel-team@fb.com
Subject: Re: [PATCH 1/2] nvme: untangle 0 and BLK_MQ_RQ_QUEUE_OK
Date: Tue, 15 Nov 2016 12:51:01 -0700 [thread overview]
Message-ID: <96ea1cf1-3d84-5e08-e55f-5d903070fed2@kernel.dk> (raw)
In-Reply-To: <ec8930a71efdc30f9d5e5c69954f5b10cfab9927.1479236597.git.osandov@fb.com>
On 11/15/2016 12:11 PM, Omar Sandoval wrote:
> From: Omar Sandoval <osandov@fb.com>
>
> Let's not depend on any of the BLK_MQ_RQ_QUEUE_* constants having
> specific values. No functional change.
Thanks Omar, applied both for 4.10.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: axboe@kernel.dk (Jens Axboe)
Subject: [PATCH 1/2] nvme: untangle 0 and BLK_MQ_RQ_QUEUE_OK
Date: Tue, 15 Nov 2016 12:51:01 -0700 [thread overview]
Message-ID: <96ea1cf1-3d84-5e08-e55f-5d903070fed2@kernel.dk> (raw)
In-Reply-To: <ec8930a71efdc30f9d5e5c69954f5b10cfab9927.1479236597.git.osandov@fb.com>
On 11/15/2016 12:11 PM, Omar Sandoval wrote:
> From: Omar Sandoval <osandov at fb.com>
>
> Let's not depend on any of the BLK_MQ_RQ_QUEUE_* constants having
> specific values. No functional change.
Thanks Omar, applied both for 4.10.
--
Jens Axboe
next prev parent reply other threads:[~2016-11-15 19:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 19:11 [PATCH 1/2] nvme: untangle 0 and BLK_MQ_RQ_QUEUE_OK Omar Sandoval
2016-11-15 19:11 ` Omar Sandoval
2016-11-15 19:11 ` [PATCH 2/2] scsi_lib: " Omar Sandoval
2016-11-15 19:11 ` Omar Sandoval
2016-11-15 19:44 ` [PATCH 1/2] nvme: " Keith Busch
2016-11-15 19:44 ` Keith Busch
2016-11-15 19:51 ` Jens Axboe [this message]
2016-11-15 19:51 ` Jens Axboe
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=96ea1cf1-3d84-5e08-e55f-5d903070fed2@kernel.dk \
--to=axboe@kernel.dk \
--cc=kernel-team@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=osandov@osandov.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.