public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] remove INT_GET and friends
Date: Mon, 07 Jul 2008 22:05:14 -0500	[thread overview]
Message-ID: <4872D96A.7070703@sandeen.net> (raw)
In-Reply-To: <47FF794C.4020801@sandeen.net>

Eric Sandeen wrote:
> Thanks to hch's endian work, INT_GET etc are no longer used,
> and may as well be removed.  INT_SET is still used in
> the acl code, though.
> 
> Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
> ---
> 
>  xfs_arch.h |   68 ---------------------------------
>  1 files changed, 68 deletions(-)
> 

Ping?  these are just unused macros.

-Eric

> 
> Index: linux-2.6-xfs/fs/xfs/xfs_arch.h
> ===================================================================
> --- linux-2.6-xfs.orig/fs/xfs/xfs_arch.h
> +++ linux-2.6-xfs/fs/xfs/xfs_arch.h
> @@ -92,16 +92,6 @@
>  	((__u8*)(pointer))[1] = (((value)     ) & 0xff); \
>      }
>  
> -/* define generic INT_ macros */
> -
> -#define INT_GET(reference,arch) \
> -    (((arch) == ARCH_NOCONVERT) \
> -	? \
> -	    (reference) \
> -	: \
> -	    INT_SWAP((reference),(reference)) \
> -    )
> -
>  /* does not return a value */
>  #define INT_SET(reference,arch,valueref) \
>      (__builtin_constant_p(valueref) ? \
> @@ -112,64 +102,6 @@
>  	) \
>      )
>  
> -/* does not return a value */
> -#define INT_MOD_EXPR(reference,arch,code) \
> -    (((arch) == ARCH_NOCONVERT) \
> -	? \
> -	    (void)((reference) code) \
> -	: \
> -	    (void)( \
> -		(reference) = INT_GET((reference),arch) , \
> -		((reference) code), \
> -		INT_SET(reference, arch, reference) \
> -	    ) \
> -    )
> -
> -/* does not return a value */
> -#define INT_MOD(reference,arch,delta) \
> -    (void)( \
> -	INT_MOD_EXPR(reference,arch,+=(delta)) \
> -    )
> -
> -/*
> - * INT_COPY - copy a value between two locations with the
> - *	      _same architecture_ but _potentially different sizes_
> - *
> - *	    if the types of the two parameters are equal or they are
> - *		in native architecture, a simple copy is done
> - *
> - *	    otherwise, architecture conversions are done
> - *
> - */
> -
> -/* does not return a value */
> -#define INT_COPY(dst,src,arch) \
> -    ( \
> -	((sizeof(dst) == sizeof(src)) || ((arch) == ARCH_NOCONVERT)) \
> -	    ? \
> -		(void)((dst) = (src)) \
> -	    : \
> -		INT_SET(dst, arch, INT_GET(src, arch)) \
> -    )
> -
> -/*
> - * INT_XLATE - copy a value in either direction between two locations
> - *	       with different architectures
> - *
> - *		    dir < 0	- copy from memory to buffer (native to arch)
> - *		    dir > 0	- copy from buffer to memory (arch to native)
> - */
> -
> -/* does not return a value */
> -#define INT_XLATE(buf,mem,dir,arch) {\
> -    ASSERT(dir); \
> -    if (dir>0) { \
> -	(mem)=INT_GET(buf, arch); \
> -    } else { \
> -	INT_SET(buf, arch, mem); \
> -    } \
> -}
> -
>  static inline void be16_add(__be16 *a, __s16 b)
>  {
>  	*a = cpu_to_be16(be16_to_cpu(*a) + b);
> 
> 
> 

  parent reply	other threads:[~2008-07-08  3:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-11 14:44 [PATCH] remove INT_GET and friends Eric Sandeen
2008-04-11 16:05 ` Christoph Hellwig
2008-07-08  3:05 ` Eric Sandeen [this message]
2008-07-08  8:02   ` Christoph Hellwig
2008-07-24  8:16 ` Niv Sardi

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=4872D96A.7070703@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.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