From: "J.A. Magallon" <jamagallon@able.es>
To: David Woodhouse <dwmw2@infradead.org>
Cc: marcelo@conectiva.com.br, alan@lxorguk.ukuu.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Shared crc32 for 2.4.
Date: Thu, 22 May 2003 01:50:33 +0200 [thread overview]
Message-ID: <20030521235033.GA2470@werewolf.able.es> (raw)
In-Reply-To: <1053193432.9218.13.camel@imladris.demon.co.uk>; from dwmw2@infradead.org on Sat, May 17, 2003 at 19:43:53 +0200
On 05.17, David Woodhouse wrote:
> This has been needed for a long time... please pull from
> master.kernel.org:/home/dwmw2/BK/crc32-2.4 or apply the GNU patch below.
>
> I can resend for 2.4.22-pre1 if you prefer, but it's been working in 2.5
> and in various other 2.4 trees for a while now so I'm sending it now
> anyway.
>
This works if crc32.o is compiled as a module, but does not work if it is
built into the kernel. For example, crc32_le symbol does not appear
in System.map nor vmlinux.
For me, it failed with 8390.o ans 8139too.o. But just because they are the
only drivers needing crc32 that I build.
TIA
--
J.A. Magallon <jamagallon@able.es> \ Software is like sex:
werewolf.able.es \ It's better when it's free
Mandrake Linux release 9.2 (Cooker) for i586
Linux 2.4.21-rc2-jam1 (gcc 3.2.3 (Mandrake Linux 9.2 3.2.3-1mdk))
next prev parent reply other threads:[~2003-05-21 23:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-17 17:43 [PATCH] Shared crc32 for 2.4 David Woodhouse
2003-05-19 7:24 ` Duncan Sands
2003-05-19 15:06 ` David Woodhouse
2003-05-21 23:50 ` J.A. Magallon [this message]
2003-05-22 21:11 ` David Woodhouse
2003-05-23 9:28 ` David Woodhouse
2003-05-22 20:23 ` Marcelo Tosatti
2003-05-23 6:44 ` David Woodhouse
[not found] <03ee01c320b4$c3040ad0$020120b0@jockeXP>
2003-05-27 11:26 ` David Woodhouse
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=20030521235033.GA2470@werewolf.able.es \
--to=jamagallon@able.es \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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