From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: [PATCH] nvme-fabrics: add-remove ctrl repeat fix
Date: Wed, 13 Jul 2016 09:16:01 -0700 [thread overview]
Message-ID: <1468426561.3223.0.camel@linux.intel.com> (raw)
In-Reply-To: <57857F6A.6000406@fb.com>
On Tue, 2016-07-12@16:38 -0700, Jens Axboe wrote:
> On 07/12/2016 04:15 PM, J Freyensee wrote:
> > On Fri, 2016-07-01@12:13 -0700, Jay Freyensee wrote:
> >
> > I haven't seen this patch get folded in on the list yet, though
> > Christoph OK'ed the fix, minus the 'Fix by:' I used instead of
> > 'From:'.
> >
> > Has this been folded into 4.8? Should I go ahead and re-spin the
> > patch
> > and make the tweak change? Be nice to eliminate this kernel crash
> > with
> > fabrics being merged into 4.8 kernel.
>
> It was added into for-4.8/drivers earlier today, with the author
> attribution fixed.
Thanks Jens!!
>
prev parent reply other threads:[~2016-07-13 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 19:13 [PATCH] nvme-fabrics: add-remove ctrl repeat fix Jay Freyensee
2016-07-04 8:48 ` Christoph Hellwig
2016-07-08 15:56 ` J Freyensee
2016-07-12 23:15 ` J Freyensee
2016-07-12 23:38 ` Jens Axboe
2016-07-13 16:16 ` J Freyensee [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=1468426561.3223.0.camel@linux.intel.com \
--to=james_p_freyensee@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).