From: James Morris <jmorris@intercode.com.au>
To: bert hubert <ahu@ds9a.nl>
Cc: linux-kernel@vger.kernel.org, "David S. Miller" <davem@redhat.com>
Subject: [PATCH] Re: 2.5.48 Compilation Failure skbuff.c
Date: Tue, 19 Nov 2002 00:14:10 +1100 (EST) [thread overview]
Message-ID: <Mutt.LNX.4.44.0211190013030.22010-100000@blackbird.intercode.com.au> (raw)
In-Reply-To: <20021118125450.GA14855@outpost.ds9a.nl>
On Mon, 18 Nov 2002, bert hubert wrote:
> On Mon, Nov 18, 2002 at 01:36:48PM +0100, Rene Blokland wrote:
> > Hello, 2.5.48 Doesn't compile for me on a AMD k6-3 with gcc-3.2 and glibc-2.3.1
>
> I bet this just made ipsec mandatory :-)
Not quite yet :-)
A fix is below.
- James
--
James Morris
<jmorris@intercode.com.au>
diff -urN -X dontdiff linux-2.5.48.orig/include/linux/crypto.h linux-2.5.48.w1/include/linux/crypto.h
--- linux-2.5.48.orig/include/linux/crypto.h Tue Nov 12 00:12:06 2002
+++ linux-2.5.48.w1/include/linux/crypto.h Tue Nov 19 00:09:39 2002
@@ -196,12 +196,7 @@
static inline const char *crypto_tfm_alg_modname(struct crypto_tfm *tfm)
{
- struct crypto_alg *alg = tfm->__crt_alg;
-
- if (alg->cra_module)
- return alg->cra_module->name;
- else
- return NULL;
+ return module_name(tfm->__crt_alg->cra_module);
}
static inline u32 crypto_tfm_alg_type(struct crypto_tfm *tfm)
next prev parent reply other threads:[~2002-11-18 13:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-18 12:36 Rene Blokland
2002-11-18 12:54 ` bert hubert
2002-11-18 13:12 ` Thomas Molina
2002-11-18 13:14 ` James Morris [this message]
2002-11-18 14:40 ` [PATCH] " Rene Blokland
2002-11-18 23:05 ` David S. Miller
2002-11-18 13:31 ` Rene Blokland
2002-11-18 13:12 ` Werner Almesberger
2002-11-18 13:23 ` Thomas Molina
2002-11-18 13:51 ` Werner Almesberger
2002-11-18 13:37 ` Rene Blokland
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=Mutt.LNX.4.44.0211190013030.22010-100000@blackbird.intercode.com.au \
--to=jmorris@intercode.com.au \
--cc=ahu@ds9a.nl \
--cc=davem@redhat.com \
--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
all inboxes | Powered by JetHome®