From: Pete Zaitcev <zaitcev@redhat.com>
To: Martin Schwidefsky <martin.schwidefsky@debitel.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.22: common code changes for s/390.
Date: Mon, 17 Jun 2002 17:02:20 -0400 [thread overview]
Message-ID: <200206172102.g5HL2K011511@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1024345597.31683.linux-kernel2news@redhat.com>
> --- linux-2.5.22/include/linux/auto_fs.h Mon Jun 17 04:31:22 2002
> +++ linux-2.5.22-s390/include/linux/auto_fs.h Tue Jun 4 09:52:06 2002
> @@ -45,7 +45,8 @@
> * If so, 32-bit user-space code should be backwards compatible.
> */
>
> -#if defined(__sparc__) || defined(__mips__) || defined(__x86_64__) || defined(__powerpc__)
> +#if defined(__sparc__) || defined(__mips__) || defined(__x86_64) \
> + || defined(__powerpc__) || defined(__s390__)
Sure it's not missing __ at the end of x86_64?
Testing if anyone reads it, are you :)
-- Pete
next parent reply other threads:[~2002-06-17 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1024345597.31683.linux-kernel2news@redhat.com>
2002-06-17 21:02 ` Pete Zaitcev [this message]
2002-06-17 22:22 [PATCH] 2.5.22: common code changes for s/390 Martin Schwidefsky
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=200206172102.g5HL2K011511@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.schwidefsky@debitel.net \
/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