Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@fusionio.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: "kreijack@inwind.it" <kreijack@inwind.it>,
	Chris Mason <clmason@fusionio.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs-progs: include kerncompat.h in raid6.c, define __attribute_const__
Date: Sun, 3 Feb 2013 12:41:56 -0500	[thread overview]
Message-ID: <20130203174156.GA25685@shiny> (raw)
In-Reply-To: <510E9FA3.5060600@redhat.com>

On Sun, Feb 03, 2013 at 10:34:27AM -0700, Eric Sandeen wrote:
> raid6.c was failing to build for Goffredo and me due to
> __attribute_const__ being undefined.

Thanks, I've pushed this along with an extra #ifndef into the raid56
experimental branch.

-chris

      reply	other threads:[~2013-02-03 17:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-02 20:13 [BTRFS-PROGS][PATCH] remove __attribute_const__ from raid6.c Goffredo Baroncelli
2013-02-03 15:56 ` Eric Sandeen
2013-02-03 16:19   ` Eric Sandeen
2013-02-03 17:01   ` David Sterba
2013-02-03 17:34     ` [PATCH] btrfs-progs: include kerncompat.h in raid6.c, define __attribute_const__ Eric Sandeen
2013-02-03 17:41       ` Chris Mason [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=20130203174156.GA25685@shiny \
    --to=chris.mason@fusionio.com \
    --cc=clmason@fusionio.com \
    --cc=kreijack@inwind.it \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sandeen@redhat.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