From: Thomas Skora <thomas@skora.net>
To: Roger Luethi <rl@hellgate.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] via-rhine.c, wol-bugfix, Kernel 2.6.11.5
Date: Thu, 24 Mar 2005 12:37:50 +0100 [thread overview]
Message-ID: <87br9946lt.fsf@powers.localnet> (raw)
In-Reply-To: <20050324074109.GA14926@k3.hellgate.ch> (Roger Luethi's message of "Thu, 24 Mar 2005 08:41:09 +0100")
Roger Luethi <rl@hellgate.ch> writes:
> This patch won't apply to the 2.6.11.5 I have here -- the driver is
> clearing ~0xFC already. The description makes me suspect that the patch
> is meant to go the other way, and that would be wrong.
You are right. I don't know what happened, but in my sources (from
kernel.org without any patches) this was cleared to 0xFE.
> Use ethtool if you want to enable WOL, default in Linux net drivers is
> off.
The problem was, that this doesn't worked.
> Please don't send patches as application/octet-stream, that's
> annoying. Send either text/plain or inline.
Ok, thank you for the hint.
Thomas
prev parent reply other threads:[~2005-03-24 11:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 0:37 [PATCH] via-rhine.c, wol-bugfix, Kernel 2.6.11.5 Thomas Skora
2005-03-24 7:41 ` Roger Luethi
2005-03-24 11:37 ` Thomas Skora [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=87br9946lt.fsf@powers.localnet \
--to=thomas@skora.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rl@hellgate.ch \
/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.