From: "David S. Miller" <davem@redhat.com>
To: karrde@callisto.yi.org
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: test11-pre5
Date: Tue, 14 Nov 2000 16:49:23 -0800 [thread overview]
Message-ID: <200011150049.QAA01994@pizda.ninka.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0011150250050.28006-100000@callisto.yi.org> (message from Dan Aloni on Wed, 15 Nov 2000 02:59:36 +0200 (IST))
In-Reply-To: <Pine.LNX.4.21.0011150250050.28006-100000@callisto.yi.org>
Date: Wed, 15 Nov 2000 02:59:36 +0200 (IST)
From: Dan Aloni <karrde@callisto.yi.org>
On Tue, 14 Nov 2000, David S. Miller wrote:
> Then the compiler will start warning us :-)
I've also noticed that routing_ioctl() in arch/mips64/kernel/ioctl32.c
assumes the 16. Are those two platforms depend on having IFNAMSIZ == 16,
or this code just needs cleaning up?
No, it means the code "may need changing" if IFNAMSIZ is ever
changed. The compiler will warn us when this happens instead
of silently compiling the code.
Later,
David S. Miller
davem@redhat.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-15 1:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-14 21:47 test11-pre5 Linus Torvalds
2000-11-14 22:45 ` [PATCH] test11-pre5 Dan Aloni
2000-11-14 22:50 ` Jeff Garzik
2000-11-14 23:10 ` Dan Aloni
2000-11-14 23:14 ` Jeff Garzik
2000-11-14 23:51 ` Linus Torvalds
2000-11-16 8:51 ` Nick Holloway
2000-11-14 23:47 ` Linus Torvalds
2000-11-15 0:25 ` Dan Aloni
2000-11-15 0:25 ` David S. Miller
2000-11-15 0:59 ` Dan Aloni
2000-11-15 0:49 ` David S. Miller [this message]
2000-11-14 22:47 ` test11-pre5 Jes Sorensen
2000-11-14 23:08 ` [uPATCH] test11-pre5 Bartlomiej Zolnierkiewicz
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=200011150049.QAA01994@pizda.ninka.net \
--to=davem@redhat.com \
--cc=karrde@callisto.yi.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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®