public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
* NVME_QUIRK_IGNORE_DEV_SUBNQN patch?
@ 2019-01-03 15:25 Gabriel Frangakis
  2019-01-08 16:55 ` Gabriel Frangakis
  0 siblings, 1 reply; 3+ messages in thread
From: Gabriel Frangakis @ 2019-01-03 15:25 UTC (permalink / raw)


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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* NVME_QUIRK_IGNORE_DEV_SUBNQN patch?
  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
  0 siblings, 1 reply; 3+ messages in thread
From: Gabriel Frangakis @ 2019-01-08 16:55 UTC (permalink / raw)


Bumping this. I can also try submitting as a patch but as a newcomer
didn't think it was appropriate

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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* NVME_QUIRK_IGNORE_DEV_SUBNQN patch?
  2019-01-08 16:55 ` Gabriel Frangakis
@ 2019-01-08 17:19   ` Keith Busch
  0 siblings, 0 replies; 3+ messages in thread
From: Keith Busch @ 2019-01-08 17:19 UTC (permalink / raw)


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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2019-01-08 17:19 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox