From: Tomi Orava <tomimo@ncircle.nullnet.fi>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andrew Morton <akpm@linux-foundation.org>,
bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org,
Stephen Hemminger <shemminger@linux-foundation.org>
Subject: Re: [Bugme-new] [Bug 12886] New: skge wake on lan
Date: Fri, 20 Mar 2009 05:59:05 +0200 [thread overview]
Message-ID: <49C31489.6080206@ncircle.nullnet.fi> (raw)
In-Reply-To: <200903192159.13170.rjw@sisk.pl>
On 03/19/2009 10:59 PM, Rafael J. Wysocki wrote:
> On Thursday 19 March 2009, Tomi Orava wrote:
>> Hi,
>>
>>> Hm, are you sure the commit in question _is_ in 2.6.28.y? I can't see it in
>>> there. It is in the current Linus' tree, but not in v2.6.28 and surely not in
>>> -stable. Do you use a distro kernel?
>> Ok, I've now verified that I did indeed mess up with the commit
>> mentioned previously. In other words the stable series 2.6.28.x
>> doesn't support the suspend feature on my Asus A7V880 at all.
>> The bios option is not respected at all and the command
>> 'ethtool -s eth0 wol g' doesn't enable the suspend any better.
>>
>> However, the commit taken from main branch actually makes also
>> the stable series to work with this motherboard. No additional
>> changes are needed, it just works out of the box.
>>
>> Sorry about the mess up.
>
> No problem.
>
> Does it mean we can close the bug?
Yes, as it does look like the next stable release should
contain the fix by default.
Thanks & Regards,
Tomi Orava
prev parent reply other threads:[~2009-03-20 3:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12886-10286@http.bugzilla.kernel.org/>
2009-03-17 3:04 ` [Bugme-new] [Bug 12886] New: skge wake on lan Andrew Morton
2009-03-17 10:01 ` Rafael J. Wysocki
2009-03-17 10:15 ` Tomi Orava
2009-03-17 21:23 ` Rafael J. Wysocki
2009-03-18 7:32 ` Tomi Orava
2009-03-18 15:14 ` Rafael J. Wysocki
2009-03-19 13:03 ` Tomi Orava
2009-03-19 16:23 ` Tomi Orava
2009-03-19 20:59 ` Rafael J. Wysocki
2009-03-20 3:59 ` Tomi Orava [this message]
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=49C31489.6080206@ncircle.nullnet.fi \
--to=tomimo@ncircle.nullnet.fi \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=shemminger@linux-foundation.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 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).