public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: NVME_QUIRK_IGNORE_DEV_SUBNQN patch?
Date: Tue, 8 Jan 2019 10:19:40 -0700	[thread overview]
Message-ID: <20190108171940.GE18014@localhost.localdomain> (raw)
In-Reply-To: <CAP5yZ1hRjj_DVJKzKXtk-Fh5Vkz+aUekkz9RAbRGDCJ0D801Fw@mail.gmail.com>

On Tue, Jan 08, 2019@11:55:03AM -0500, Gabriel Frangakis wrote:
> Bumping this. I can also try submitting as a patch but as a newcomer
> didn't think it was appropriate

New contributers are certainly welcome.

I think James' patch was fine, but I don't see that it was ever posted
as a proper patch that could be applied. I'll send one on his behalf
with a review tag.

> On Thu, Jan 3, 2019 at 10:25 AM Gabriel Frangakis
> <gabe.frangakis@gmail.com> wrote:
> >
> > Back in November, there was a discussion about a firmware issue with
> > Intel NVME drives
> > (http://lists.infradead.org/pipermail/linux-nvme/2018-November/021366.html).
> > Intel has issued a firmware update to address this, but there's no
> > telling when OEMs will pick it up and incorporate it.
> >
> > It seemed that a potential fix was created by John Dingwall to ignore
> > the sub NQN, and I was wondering if there were plans to submit this as
> > a patch to the kernel. I'm unfamiliar with how that whole process
> > works, so apologies if I'm out of line.

      reply	other threads:[~2019-01-08 17:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03 15:25 NVME_QUIRK_IGNORE_DEV_SUBNQN patch? Gabriel Frangakis
2019-01-08 16:55 ` Gabriel Frangakis
2019-01-08 17:19   ` Keith Busch [this message]

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=20190108171940.GE18014@localhost.localdomain \
    --to=keith.busch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox