[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190705051733.GA15821@kroah.com>
Date: Fri, 5 Jul 2019 07:17:33 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: David Howells <dhowells@...hat.com>
Cc: viro@...iv.linux.org.uk, Casey Schaufler <casey@...aufler-ca.com>,
Stephen Smalley <sds@...ho.nsa.gov>, nicolas.dichtel@...nd.com,
raven@...maw.net, Christian Brauner <christian@...uner.io>,
keyrings@...r.kernel.org, linux-usb@...r.kernel.org,
linux-security-module@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-api@...r.kernel.org,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 6/9] Add a general, global device notification watch list
[ver #5]
On Thu, Jul 04, 2019 at 05:04:20PM +0100, David Howells wrote:
> Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
>
> > Don't we need a manpage and a kselftest for it?
>
> I've got part of a manpage, but it needs more work.
>
> How do you do a kselftest for this when it does nothing unless hardware events
> happen?
Hm, good point, but there should be some way to test this to verify it
works. Maybe for the other types of events?
thanks,
greg k-h
Powered by blists - more mailing lists