From: keith.busch@intel.com (Keith Busch)
Subject: [PATCHv2 5/5] nvme: Send uevent for unhandled AEN completions
Date: Mon, 30 Oct 2017 09:18:01 -0600 [thread overview]
Message-ID: <20171030151800.GC17245@localhost.localdomain> (raw)
In-Reply-To: <b05dcfac-0d50-4b90-544e-646bbfce57bb@huawei.com>
On Mon, Oct 30, 2017@06:14:30PM +0800, Guan Junxiong wrote:
>
> On 2017/10/21 6:37, Keith Busch wrote:
> > static void nvme_async_event_work(struct work_struct *work)
> > {
> > struct nvme_ctrl *ctrl =
> > container_of(work, struct nvme_ctrl, async_event_work);
> >
> > + nvme_aen_uevent(ctrl);
> > ctrl->ops->submit_async_event(ctrl);
> > }
>
> Is this based on 4.15 or 4.14? I failed to apply it.
>
This was based off this branch:
http://git.infradead.org/nvme.git/shortlog/refs/heads/nvme-4.15
starting from commit 134aedc9c ("nvme-fc: correct io timeout behavior")
next prev parent reply other threads:[~2017-10-30 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 22:37 [PATCHv2 5/5] nvme: Send uevent for unhandled AEN completions Keith Busch
2017-10-21 8:09 ` Christoph Hellwig
2017-10-23 15:01 ` Keith Busch
2017-10-30 10:14 ` Guan Junxiong
2017-10-30 15:18 ` Keith Busch [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-20 22:19 [PATCHv2 0/5] AEN and userspace updates Keith Busch
2017-10-20 22:19 ` [PATCHv2 5/5] nvme: Send uevent for unhandled AEN completions Keith Busch
2017-10-20 22:29 ` Keith Busch
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=20171030151800.GC17245@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 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.