From: Cornelia Huck <cohuck@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kwankhede@nvidia.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mdev: Send uevents around parent device registration
Date: Mon, 1 Jul 2019 17:06:56 +0200 [thread overview]
Message-ID: <20190701170656.6ac05101.cohuck@redhat.com> (raw)
In-Reply-To: <156199271955.1646.13321360197612813634.stgit@gimli.home>
On Mon, 01 Jul 2019 08:54:44 -0600
Alex Williamson <alex.williamson@redhat.com> wrote:
> This allows udev to trigger rules when a parent device is registered
> or unregistered from mdev.
>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> ---
>
> v2: Don't remove the dev_info(), Kirti requested they stay and
> removing them is only tangential to the goal of this change.
>
> drivers/vfio/mdev/mdev_core.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
Not that fond of the dev_info(), but this still looks sane.
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2019-07-01 15:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 14:54 [PATCH v2] mdev: Send uevents around parent device registration Alex Williamson
2019-07-01 15:06 ` Cornelia Huck [this message]
2019-07-01 17:13 ` Kirti Wankhede
2019-07-01 17:24 ` Alex Williamson
2019-07-01 17:50 ` Kirti Wankhede
2019-07-01 20:04 ` Alex Williamson
2019-07-02 4:55 ` Kirti Wankhede
2019-07-02 5:42 ` Alex Williamson
2019-07-02 7:13 ` Parav Pandit
2019-07-02 12:47 ` Kirti Wankhede
2019-07-02 13:08 ` Alex Williamson
2019-07-02 13:40 ` Kirti Wankhede
2019-07-02 14:43 ` Alex Williamson
2019-07-02 18:04 ` Kirti Wankhede
2019-07-02 18:31 ` Alex Williamson
2019-07-02 5:46 ` Cornelia Huck
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=20190701170656.6ac05101.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
/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.