arch maintainers: define O_CLOEXEC correctly!

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

A few architectures still don't have a correct O_CLOEXEC definition.
The default definition in <asm-generic/fcntl.h> is wrong for some archs
and you really don't want see 2.6.23 released with a broken ABI.

Affected as far as I know:

Alpha:   probably needs value 010000000

Sparc*:         -"-           0x400000

- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFGs2E82ijCOnn/RHQRArC+AKCT+/od1qzfC8t7r6jobwd7WS5nOwCgqlzn
ugozxlOLdgTVG0XMsJx0x7Q=
=PinC
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: arch maintainers: define O_CLOEXEC correctly!
    • From: Richard Henderson <[email protected]>
  • Re: arch maintainers: define O_CLOEXEC correctly!
    • From: David Miller <[email protected]>

• Prev by Date: Re: [NFS] 2.6.23-rc1-mm2
• Next by Date: Re: [NFS] 2.6.23-rc1-mm2
• Previous by thread: libata git tree, mbox queue status and contents
• Next by thread: Re: arch maintainers: define O_CLOEXEC correctly!
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]