From: Dave Jones <davej@suse.de>
To: Denis Zaitsev <zzz@cd-club.ru>
Cc: Keith Owens <kaos@ocs.com.au>,
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: FIXED_486_STRING ?
Date: Mon, 15 Apr 2002 03:36:59 +0200 [thread overview]
Message-ID: <20020415033659.E20383@suse.de> (raw)
In-Reply-To: <20020413224743.A13355@natasha.zzz.zzz> <32667.1018744038@ocs3.intra.ocs.com.au> <20020414024406.A16692@suse.de> <20020415063825.A2691@natasha.zzz.zzz> <20020415030355.D20383@suse.de> <20020415072556.A2839@natasha.zzz.zzz>
On Mon, Apr 15, 2002 at 07:25:56AM +0600, Denis Zaitsev wrote:
> On Mon, Apr 15, 2002 at 03:03:55AM +0200, Dave Jones wrote:
> > Petko Manolov <lz5mj@yahoo.com> did some work on them circa 2.4.0test.
> > His patch is at http://www.dce.bg/~petkan/linux/string-486.diff
> These patches are included...
Look again.
(davej@noodles:linux-2.4.19-pre6)$ cat ../string-486.diff | patch -p1 -F1 --dry-run
patching file include/asm-i386/string-486.h
Hunk #13 FAILED at 365.
Hunk #14 succeeded at 388 (offset -5 lines).
Hunk #15 succeeded at 409 (offset -5 lines).
Hunk #16 succeeded at 452 (offset -5 lines).
Hunk #17 succeeded at 516 (offset -5 lines).
1 out of 17 hunks FAILED -- saving rejects to file include/asm-i386/string-486.h.rej
Almost still applies except for one hunk.
> But the string-486.h itself is turned
> off by FIXED_486_STRING. BTW, what are the problems?
Not sure off-hand. I would hazard a guess that they copied
too little/too much, but Petko would be a better person
to ask.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-04-15 1:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-13 16:47 FIXED_486_STRING ? Denis Zaitsev
2002-04-14 0:27 ` Keith Owens
2002-04-14 0:44 ` Dave Jones
2002-04-15 0:38 ` Denis Zaitsev
2002-04-15 1:03 ` Dave Jones
2002-04-15 1:25 ` Denis Zaitsev
2002-04-15 1:36 ` Dave Jones [this message]
2002-04-15 1:46 ` Denis Zaitsev
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=20020415033659.E20383@suse.de \
--to=davej@suse.de \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=zzz@cd-club.ru \
/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