linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] include: don't collide __bitwise definitions in 4.10
Date: Tue, 21 Feb 2017 12:16:24 -0600	[thread overview]
Message-ID: <c9d0ac33-43df-1062-e71d-1df071dbba60@redhat.com> (raw)
In-Reply-To: <20170221180525.GG5846@birch.djwong.org>

On 2/21/17 12:05 PM, Darrick J. Wong wrote:
> Linux 4.10 changed the definition of __bitwise in such a way that
> xfsprogs' definition is no longer a strict match for it.  This causes
> gcc to complain, so only #define it here if the system hasn't already
> done it for us.
> 
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>

Makes sense, thanks for catching this.

Reviewed-by: Eric Sandeen <sandeen@redhat.com>

> ---
>  include/xfs_arch.h |    8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/include/xfs_arch.h b/include/xfs_arch.h
> index 6e3172c..12cd43e 100644
> --- a/include/xfs_arch.h
> +++ b/include/xfs_arch.h
> @@ -25,10 +25,14 @@
>  #endif
>  
>  #ifdef __CHECKER__
> -#define __bitwise		__attribute__((bitwise))
> +# ifndef __bitwise
> +#  define __bitwise		__attribute__((bitwise))
> +# endif
>  #define __force			__attribute__((force))
>  #else
> -#define __bitwise
> +# ifndef __bitwise
> +#  define __bitwise
> +# endif
>  #define __force
>  #endif
>  
> 


      reply	other threads:[~2017-02-21 18:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 18:05 [PATCH] include: don't collide __bitwise definitions in 4.10 Darrick J. Wong
2017-02-21 18:16 ` Eric Sandeen [this message]

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=c9d0ac33-43df-1062-e71d-1df071dbba60@redhat.com \
    --to=sandeen@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).