mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: cs@pixelwings.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.33 compile error in ipv6
Date: Mon, 02 Sep 2002 16:25:42 -0700 (PDT)	[thread overview]
Message-ID: <20020902.162542.95902127.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0209021304590.2696-100000@lynx.piwi.intern>

   From: Clemens Schwaighofer <cs@pixelwings.com>
   Date: Mon, 2 Sep 2002 13:06:13 +0200 (CEST)
   
   I saw no patch in ML yet for this ...

Actually, there was, lines 666 and 667 of net/ipv6/af_inet6.c
should read:

                printk(KERN_CRIT "%s: Can't create protocol sock SLAB "
                       "caches!\n", __FUNCTION__);

Here is the patch against 2.5.33 that James Morris posted.

diff -Nru a/net/ipv6/af_inet6.c b/net/ipv6/af_inet6.c
--- a/net/ipv6/af_inet6.c       Mon Sep  2 16:28:13 2002
+++ b/net/ipv6/af_inet6.c       Mon Sep  2 16:28:13 2002
@@ -663,8 +663,8 @@
                                           sizeof(struct raw6_sock), 0,
                                            SLAB_HWCACHE_ALIGN, 0, 0);
         if (!tcp6_sk_cachep || !udp6_sk_cachep || !raw6_sk_cachep)
-                printk(KERN_CRIT __FUNCTION__
-                        ": Can't create protocol sock SLAB caches!\n");
+                printk(KERN_CRIT "%s: Can't create protocol sock SLAB "
+                      "caches!\n", __FUNCTION__);

        /* Register the socket-side information for inet6_create.  */
        for(r = &inetsw6[0]; r < &inetsw6[SOCK_MAX]; ++r)

      reply	other threads:[~2002-09-02 23:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-02 11:06 Clemens Schwaighofer
2002-09-02 23:25 ` David S. Miller [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=20020902.162542.95902127.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=cs@pixelwings.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®