From: keith.busch@intel.com (Keith Busch)
Subject: [PATCHv2 5/5] nvme: Send uevent for unhandled AEN completions
Date: Fri, 20 Oct 2017 16:29:32 -0600 [thread overview]
Message-ID: <20171020222932.GA30713@localhost.localdomain> (raw)
In-Reply-To: <20171020221924.30659-6-keith.busch@intel.com>
On Fri, Oct 20, 2017@04:19:24PM -0600, Keith Busch wrote:
> +static void nvme_aen_uevent(struct nvme_ctrl *ctrl)
> +{
> + char *envp[2] = {NULL, NULL};
> + u32 aen = ctrl->aen;
> +
> + ctrl->aen = 0;
> + if (!aen)
> + return;
> +
> + if (!envp[0])
> + return;
> + kobject_uevent_env(&ctrl->device->kobj, KOBJ_CHANGE, envp);
> + kfree(envp[0]);
> +}
Uh, the string format dissappeared on me. Resending...
next prev parent reply other threads:[~2017-10-20 22:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 22:19 [PATCHv2 0/5] AEN and userspace updates Keith Busch
2017-10-20 22:19 ` [PATCHv2 1/5] nvme: Centralize AEN defines Keith Busch
2017-10-21 8:06 ` Christoph Hellwig
2017-10-20 22:19 ` [PATCHv2 2/5] nvme/fc: remove unused "queue_size" field Keith Busch
2017-10-20 23:06 ` James Smart
2017-10-20 22:19 ` [PATCHv2 3/5] nvme: Single AEN request Keith Busch
2017-10-21 8:06 ` Christoph Hellwig
2017-10-20 22:19 ` [PATCHv2 4/5] nvme: Unexport starting async event work Keith Busch
2017-10-21 8:07 ` Christoph Hellwig
2017-10-20 22:19 ` [PATCHv2 5/5] nvme: Send uevent for unhandled AEN completions Keith Busch
2017-10-20 22:29 ` Keith Busch [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-20 22:37 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
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=20171020222932.GA30713@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;
as well as URLs for NNTP newsgroup(s).