linux-kernel - Re: [PATCH] ACPI / WAKEUP : enable wakeup power for physical child devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20141201111125.GA11974@localhost.localdomain>
Date:	Mon, 1 Dec 2014 14:11:25 +0300
From:	Andrey Skvortsov <andrej.skvortzov@...il.com>
To:	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ACPI / WAKEUP : enable wakeup power for physical child
 devices

On Mon, Dec 01, 2014 at 02:15:36AM +0100, Rafael J. Wysocki wrote:

> > > 
> > > -> dev->wakeup.prepare_count here shold be different from 0 at this point.
> > 
> > Thank you very much for the tip. I checked prepare_count, it was 0.
> > I tried fix that and patched ssb and b44 drivers, that are used for my Ethernet card.
> > The code is below. Is this a better way to solve this problem? 
> 
> Having a cursory look at the changes only, I think so.

Thank you, then I will format the patch in a proper way and submit it.

> > diff --git a/drivers/net/ethernet/broadcom/b44.c b/drivers/net/ethernet/broadcom/b44.c
> > index 416620f..ebac411 100644
> > --- a/drivers/net/ethernet/broadcom/b44.c
> > +++ b/drivers/net/ethernet/broadcom/b44.c
> > @@ -2103,7 +2103,9 @@ static int b44_set_wol(struct net_device *dev, struct ethtool_wolinfo *wol)
> >  	else
> >  		bp->flags &= ~B44_FLAG_WOL_ENABLE;

-- 
Best regards,
Andrey Skvortsov

PGP Key ID: 0x57A3AEAD
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/