On Wed 2016-12-21 15:42:05, Valdis Kletnieks wrote:
> Yes, I know that usually out-of-tree modules are on their own.
> However, this one may require a rethink..
>
> (Sorry for not catching this sooner, I hadn't tried to deal with the
> affected module since this patch hit linux-next in next-201611
On Wed, Dec 21, 2016 at 03:42:05PM -0500, Valdis Kletnieks wrote:
> Yes, I know that usually out-of-tree modules are on their own.
> However, this one may require a rethink..
>
> (Sorry for not catching this sooner, I hadn't tried to deal with the
> affected module since this patch hit linux-next
On Wed, Dec 21, 2016 at 03:42:05PM -0500, Valdis Kletnieks wrote:
> Yes, I know that usually out-of-tree modules are on their own.
> However, this one may require a rethink..
>
> (Sorry for not catching this sooner, I hadn't tried to deal with the
> affected module since this patch hit linux-next
+++ Valdis Kletnieks [21/12/16 15:42 -0500]:
Yes, I know that usually out-of-tree modules are on their own.
However, this one may require a rethink..
(Sorry for not catching this sooner, I hadn't tried to deal with the
affected module since this patch hit linux-next in next-20161128)
commit 7fd
Yes, I know that usually out-of-tree modules are on their own.
However, this one may require a rethink..
(Sorry for not catching this sooner, I hadn't tried to deal with the
affected module since this patch hit linux-next in next-20161128)
commit 7fd8329ba502ef76dd91db561c7aed696b2c7720
Author: P
5 matches
Mail list logo