From: Andreas Schwab <schwab@suse.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.24: auto_fs.h typo.
Date: Wed, 26 Jun 2002 14:31:41 +0200 [thread overview]
Message-ID: <je7kkm8bma.fsf@sykes.suse.de> (raw)
In-Reply-To: <afb4im$6nl$1@cesium.transmeta.com> ("H. Peter Anvin"'s message of "25 Jun 2002 18:15:02 -0700")
"H. Peter Anvin" <hpa@zytor.com> writes:
|> Followup to: <200206251759.34690.schwidefsky@de.ibm.com>
|> By author: Martin Schwidefsky <schwidefsky@de.ibm.com>
|> In newsgroup: linux.dev.kernel
|> >
|> > Hi Linus,
|> > my last patch for include/linux/auto_fs.h contained a typo that removed the
|> > trailing underscores from __x86_64__.
|> >
|> > blue skies,
|> > Martin.
|> >
|> > diff -urN linux-2.5.24/include/linux/auto_fs.h linux-2.5.24-s390/include/linux/auto_fs.h
|> > --- linux-2.5.24/include/linux/auto_fs.h Fri Jun 21 00:53:40 2002
|> > +++ linux-2.5.24-s390/include/linux/auto_fs.h Fri Jun 21 14:46:59 2002
|> > @@ -45,7 +45,7 @@
|> > * If so, 32-bit user-space code should be backwards compatible.
|> > */
|> >
|> > -#if defined(__sparc__) || defined(__mips__) || defined(__x86_64) \
|> > +#if defined(__sparc__) || defined(__mips__) || defined(__x86_64__) \
|> > || defined(__powerpc__) || defined(__s390__)
|> > typedef unsigned int autofs_wqt_t;
|> > #else
|> >
|>
|> Please change this to:
|>
|> #ifndef __alpha__
What about __ia64__?
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2002-06-26 12:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-25 15:59 [PATCH] 2.5.24: auto_fs.h typo Martin Schwidefsky
2002-06-26 1:15 ` H. Peter Anvin
2002-06-26 12:31 ` Andreas Schwab [this message]
2002-06-26 14:23 ` H. Peter Anvin
2002-06-27 3:58 ` David Mosberger
2002-06-27 14:24 ` H. Peter Anvin
2002-07-01 20:14 ` David Mosberger
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=je7kkm8bma.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=hpa@zytor.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