linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [patch 6/6] delete unused file
@ 2004-12-26 15:33 domen
  2004-12-26 17:13 ` Alan Cox
  0 siblings, 1 reply; 5+ messages in thread
From: domen @ 2004-12-26 15:33 UTC (permalink / raw)
  To: akpm; +Cc: linux-kernel, domen


Remove nowhere referenced file. (egrep "filename\." didn't find anything)

Signed-off-by: Domen Puncer <domen@coderock.org>
---


 kj/include/linux/byteorder/pdp_endian.h |   88 --------------------------------
 1 files changed, 88 deletions(-)

diff -L include/linux/byteorder/pdp_endian.h -puN include/linux/byteorder/pdp_endian.h~remove_file-include_linux_byteorder_pdp_endian.h /dev/null
--- kj/include/linux/byteorder/pdp_endian.h
+++ /dev/null	2004-12-24 01:21:08.000000000 +0100
@@ -1,88 +0,0 @@
-#ifndef _LINUX_BYTEORDER_PDP_ENDIAN_H
-#define _LINUX_BYTEORDER_PDP_ENDIAN_H
-
-/*
- * Could have been named NUXI-endian, but we use the same name as in glibc.
- * hopefully only the PDP and its evolutions (old VAXen in compatibility mode)
- * should ever use this braindead byteorder.
- * This file *should* work, but has not been tested.
- *
- * little-endian is 1234; big-endian is 4321; nuxi/pdp-endian is 3412
- *
- * I thought vaxen were NUXI-endian, but was told they were correct-endian
- * (little-endian), though indeed there existed NUXI-endian machines
- * (DEC PDP-11 and old VAXen in compatibility mode).
- * This makes this file a bit useless, but as a proof-of-concept.
- *
- * But what does a __u64 look like: is it 34127856 or 78563412 ???
- * I don't dare imagine! Hence, no 64-bit byteorder support yet.
- * Hopefully, there 64-bit pdp-endian support shouldn't ever be required.
- *
- */
-
-#ifndef __PDP_ENDIAN
-#define __PDP_ENDIAN 3412
-#endif
-#ifndef __PDP_ENDIAN_BITFIELD
-#define __PDP_ENDIAN_BITFIELD
-#endif
-
-#include <linux/byteorder/swab.h>
-#include <linux/byteorder/swabb.h>
-
-#define __constant_htonl(x) ___constant_swahb32((x))
-#define __constant_ntohl(x) ___constant_swahb32((x))
-#define __constant_htons(x) ___constant_swab16((x))
-#define __constant_ntohs(x) ___constant_swab16((x))
-#define __constant_cpu_to_le64(x) I DON'T KNOW
-#define __constant_le64_to_cpu(x) I DON'T KNOW
-#define __constant_cpu_to_le32(x) ___constant_swahw32((x))
-#define __constant_le32_to_cpu(x) ___constant_swahw32((x))
-#define __constant_cpu_to_le16(x) ((__u16)(x)
-#define __constant_le16_to_cpu(x) ((__u16)(x)
-#define __constant_cpu_to_be64(x) I DON'T KNOW
-#define __constant_be64_to_cpu(x) I DON'T KNOW
-#define __constant_cpu_to_be32(x) ___constant_swahb32((x))
-#define __constant_be32_to_cpu(x) ___constant_swahb32((x))
-#define __constant_cpu_to_be16(x) ___constant_swab16((x))
-#define __constant_be16_to_cpu(x) ___constant_swab16((x))
-#define __cpu_to_le64(x) I DON'T KNOW
-#define __le64_to_cpu(x) I DON'T KNOW
-#define __cpu_to_le32(x) ___swahw32((x))
-#define __le32_to_cpu(x) ___swahw32((x))
-#define __cpu_to_le16(x) ((__u16)(x)
-#define __le16_to_cpu(x) ((__u16)(x)
-#define __cpu_to_be64(x) I DON'T KNOW
-#define __be64_to_cpu(x) I DON'T KNOW
-#define __cpu_to_be32(x) __swahb32((x))
-#define __be32_to_cpu(x) __swahb32((x))
-#define __cpu_to_be16(x) __swab16((x))
-#define __be16_to_cpu(x) __swab16((x))
-#define __cpu_to_le64p(x) I DON'T KNOW
-#define __le64_to_cpup(x) I DON'T KNOW
-#define __cpu_to_le32p(x) ___swahw32p((x))
-#define __le32_to_cpup(x) ___swahw32p((x))
-#define __cpu_to_le16p(x) (*(__u16*)(x))
-#define __le16_to_cpup(x) (*(__u16*)(x))
-#define __cpu_to_be64p(x) I DON'T KNOW
-#define __be64_to_cpup(x) I DON'T KNOW
-#define __cpu_to_be32p(x) __swahb32p((x))
-#define __be32_to_cpup(x) __swahb32p((x))
-#define __cpu_to_be16p(x) __swab16p((x))
-#define __be16_to_cpup(x) __swab16p((x))
-#define __cpu_to_le64s(x) I DON'T KNOW
-#define __le64_to_cpus(x) I DON'T KNOW
-#define __cpu_to_le32s(x) ___swahw32s((x))
-#define __le32_to_cpus(x) ___swahw32s((x))
-#define __cpu_to_le16s(x) do {} while (0)
-#define __le16_to_cpus(x) do {} while (0)
-#define __cpu_to_be64s(x) I DON'T KNOW
-#define __be64_to_cpus(x) I DON'T KNOW
-#define __cpu_to_be32s(x) __swahb32s((x))
-#define __be32_to_cpus(x) __swahb32s((x))
-#define __cpu_to_be16s(x) __swab16s((x))
-#define __be16_to_cpus(x) __swab16s((x))
-
-#include <linux/byteorder/generic.h>
-
-#endif /* _LINUX_BYTEORDER_PDP_ENDIAN_H */
_

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [patch 6/6] delete unused file
  2004-12-26 15:33 [patch 6/6] delete unused file domen
@ 2004-12-26 17:13 ` Alan Cox
  2005-01-04 21:03   ` Matt Mackall
  0 siblings, 1 reply; 5+ messages in thread
From: Alan Cox @ 2004-12-26 17:13 UTC (permalink / raw)
  To: domen; +Cc: akpm, Linux Kernel Mailing List

On Sul, 2004-12-26 at 15:33, domen@coderock.org wrote:
> Remove nowhere referenced file. (egrep "filename\." didn't find anything)

This file is there for a reason - it completes the set of endian types
should anyone port to a mixed endian system.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [patch 6/6] delete unused file
  2004-12-26 17:13 ` Alan Cox
@ 2005-01-04 21:03   ` Matt Mackall
  2005-01-04 21:14     ` Oliver Neukum
  2005-01-06 16:30     ` Alan Cox
  0 siblings, 2 replies; 5+ messages in thread
From: Matt Mackall @ 2005-01-04 21:03 UTC (permalink / raw)
  To: Alan Cox; +Cc: domen, akpm, Linux Kernel Mailing List

On Sun, Dec 26, 2004 at 05:13:00PM +0000, Alan Cox wrote:
> On Sul, 2004-12-26 at 15:33, domen@coderock.org wrote:
> > Remove nowhere referenced file. (egrep "filename\." didn't find anything)
> 
> This file is there for a reason - it completes the set of endian types
> should anyone port to a mixed endian system.

Please name one such box that doesn't support a more sensible order
and is vaguely Linux-capable. The PDP-11 does not qualify, as it's
only 16-bit and could be made to DTRT for 32-bit values in the
compiler if you were going to go to the trouble of making "int" and
"void *" 32 bits on a 16-bit arch and then trying to fit the
resulting bloated code in the 4MB the later PDP-11s supported.

This file is silly.

-- 
Mathematics is the supreme nostalgia of our time.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [patch 6/6] delete unused file
  2005-01-04 21:03   ` Matt Mackall
@ 2005-01-04 21:14     ` Oliver Neukum
  2005-01-06 16:30     ` Alan Cox
  1 sibling, 0 replies; 5+ messages in thread
From: Oliver Neukum @ 2005-01-04 21:14 UTC (permalink / raw)
  To: Matt Mackall; +Cc: Alan Cox, domen, akpm, Linux Kernel Mailing List

Am Dienstag, 4. Januar 2005 22:03 schrieb Matt Mackall:
> On Sun, Dec 26, 2004 at 05:13:00PM +0000, Alan Cox wrote:
> > On Sul, 2004-12-26 at 15:33, domen@coderock.org wrote:
> > > Remove nowhere referenced file. (egrep "filename\." didn't find anything)
> > 
> > This file is there for a reason - it completes the set of endian types
> > should anyone port to a mixed endian system.
> 
> Please name one such box that doesn't support a more sensible order
> and is vaguely Linux-capable. The PDP-11 does not qualify, as it's
> only 16-bit and could be made to DTRT for 32-bit values in the
> compiler if you were going to go to the trouble of making "int" and
> "void *" 32 bits on a 16-bit arch and then trying to fit the
> resulting bloated code in the 4MB the later PDP-11s supported.

You don't a machine that will have the endianness. As long as you exchange
data in that format, you'll have to convert endianness.

	Regards
		Oliver

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [patch 6/6] delete unused file
  2005-01-04 21:03   ` Matt Mackall
  2005-01-04 21:14     ` Oliver Neukum
@ 2005-01-06 16:30     ` Alan Cox
  1 sibling, 0 replies; 5+ messages in thread
From: Alan Cox @ 2005-01-06 16:30 UTC (permalink / raw)
  To: Matt Mackall; +Cc: domen, akpm, Linux Kernel Mailing List

On Maw, 2005-01-04 at 21:03, Matt Mackall wrote:
> On Sun, Dec 26, 2004 at 05:13:00PM +0000, Alan Cox wrote:
> > On Sul, 2004-12-26 at 15:33, domen@coderock.org wrote:
> > > Remove nowhere referenced file. (egrep "filename\." didn't find anything)
> > 
> > This file is there for a reason - it completes the set of endian types
> > should anyone port to a mixed endian system.
> 
> Please name one such box that doesn't support a more sensible order
> and is vaguely Linux-capable.

That isnt the point of having a neat set of complete headers sometimes.

Alan


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2005-01-06 17:35 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-12-26 15:33 [patch 6/6] delete unused file domen
2004-12-26 17:13 ` Alan Cox
2005-01-04 21:03   ` Matt Mackall
2005-01-04 21:14     ` Oliver Neukum
2005-01-06 16:30     ` Alan Cox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).