From mboxrd@z Thu Jan  1 00:00:00 1970
From: roland@kernel.org (Roland Dreier)
Date: Thu, 2 Mar 2017 11:04:48 -0800
Subject: [PATCH] nvme: Correct NVMF enum values to match NVMe-oF rev 1.0
In-Reply-To: <20170302183425.GA6857@localhost.localdomain>
References: <20170302022201.2946-1-roland@kernel.org>
 <20170302155242.GA31807@infradead.org>
 <20170302160227.GD14852@localhost.localdomain>
 <20170302155613.GA9623@infradead.org>
 <CAG4TOxM-2Xs55ja1jWcGEbjez0K3ofcf5_7mH1D+Zzz09MLeyQ@mail.gmail.com>
 <20170302183425.GA6857@localhost.localdomain>
Message-ID: <CAG4TOxMPjGVsyUMVrr4J15Yyt_EDOq9DxCrhUseS=80TkCnXvw@mail.gmail.com>

On Thu, Mar 2, 2017@10:34 AM, Keith Busch <keith.busch@intel.com> wrote:
> Just considering the convenience, I can pull github requests from just about
> anywhere in the world with one click on my phone. It's a slightly more
> involved process to apply email patches. :)
>
> I'm really okay with either, though substantial changes should be sent to
> the mailing list first since that is our single source of all linux-nvme
> related reviewers. I currently rely on our best judgement to decide what's
> mailing list material, but if Christoph or anyone is really concerned
> about this, I will concede the mailing list as the preferred path.

It's easy enough to do both, I'll do that for the second fix I have now.

 - R.