From: Dave Jones <davej@suse.de>
To: dd8ne@bnv-bamberg.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.7 does not compile
Date: Fri, 22 Mar 2002 09:34:39 +0100 [thread overview]
Message-ID: <20020322093439.S22861@suse.de> (raw)
In-Reply-To: <3C9A0735.8999EBB3@wanadoo.fr> <20020321173953.F22861@suse.de> <20020322.6534800@dd8ne.ofr.de.ampr.org>
On Fri, Mar 22, 2002 at 06:53:48AM +0000, Hans-Joachim Hetscher wrote:
> It seeems to be the same bug in 6pack.c
> So, I solved the problem in line 259 of 6pack.c by changing
> dev->last_rx = jiffies;
> into
> sp->dev->last_rx = jiffies;
Yeah, it's a mystery how these broken versions of the fixes ended up
in Jeff's tree. He took them from my tree, and my tree already has this
and the previous corrected fix. really weird.
anyways, it's moot as all this is going to Jeff at the end of the week
anyway for his pushing to Linus on his return the following week 8-)
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
prev parent reply other threads:[~2002-03-22 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 16:15 2.5.7 does not compile Jean-Luc Coulon
2002-03-21 16:34 ` Evgeniy Polyakov
2002-03-21 16:39 ` Dave Jones
2002-03-22 6:53 ` Hans-Joachim Hetscher
2002-03-22 8:34 ` Dave Jones [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=20020322093439.S22861@suse.de \
--to=davej@suse.de \
--cc=dd8ne@bnv-bamberg.de \
--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