From: Roger Luethi <rl@hellgate.ch>
To: "O'Riordan, Kevin" <K.ORiordan@ucc.ie>
Cc: "'Joseph Wenninger'" <kernel@jowenn.at>, linux-kernel@vger.kernel.org
Subject: Re: Problem with Via Rhine- Kernel 2.4.18
Date: Wed, 17 Jul 2002 16:35:19 +0200 [thread overview]
Message-ID: <20020717143519.GA16992@k3.hellgate.ch> (raw)
In-Reply-To: <9FBB394A25826C46B2C6F0EBDAD42755018E6E45@xch2.ucc.ie>
> in May which fixed the problem and a new patch just a few days ago against
> 2.4.19-rc1(and against 2.4.19-rc2 as well I'd say as the via-rhine driver
Actually, the patch is against Jeff's public tree, which is somewhat
different from what's in rc1, against which I guess the patch will succeed
with offsets (rejecting the changelog portion, which is okay).
You can also try the ac kernel. Alan has the Rhine changes merged since
2.4.19-rc1-ac6.
Roger
next prev parent reply other threads:[~2002-07-17 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 9:08 Problem with Via Rhine- Kernel 2.4.18 O'Riordan, Kevin
2002-07-17 14:35 ` Roger Luethi [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-17 16:19 O'Riordan, Kevin
2002-07-17 8:35 Joseph Wenninger
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=20020717143519.GA16992@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=K.ORiordan@ucc.ie \
--cc=kernel@jowenn.at \
--cc=linux-kernel@vger.kernel.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