mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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:25:46 -0800	[thread overview]
Message-ID: <200011150025.QAA01893@pizda.ninka.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0011150216460.28006-100000@callisto.yi.org> (message from Dan Aloni on Wed, 15 Nov 2000 02:25:38 +0200 (IST))
In-Reply-To: <Pine.LNX.4.21.0011150216460.28006-100000@callisto.yi.org>

   Date: 	Wed, 15 Nov 2000 02:25:38 +0200 (IST)
   From: Dan Aloni <karrde@callisto.yi.org>

   Agreed. BTW, after grepping for IFNAMSIZ references I've noticed
   some architectures (sparc64, mips64) define IFNAMSIZ for
   themsleves, for example, arch/sparc64/kernel/ioctl32.c, which
   defines it to 16, the same include/linux/if.h does. But if they are
   not the same?

Then the compiler will start warning us :-)

#define FOO 6
#define FOO 6
int main(void)
{
	return FOO;
}
? gcc -Wall -o test test.c
? 
#define FOO 6
#define FOO 7
int main(void)
{
	return FOO;
}
? gcc -Wall -o test test.c
test.c:2: warning: `FOO' redefined
test.c:1: warning: this is the location of the previous definition
?

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/

  reply	other threads:[~2000-11-15  1:11 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 [this message]
2000-11-15  0:59         ` Dan Aloni
2000-11-15  0:49           ` David S. Miller
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=200011150025.QAA01893@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®