All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>, Eric Sandeen <sandeen@redhat.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfsprogs: enable sparse checking
Date: Fri, 24 Oct 2014 08:53:59 -0500	[thread overview]
Message-ID: <544A59F7.4070601@sandeen.net> (raw)
In-Reply-To: <20141024061718.GA15341@infradead.org>

On 10/24/14 1:17 AM, Christoph Hellwig wrote:
> On Thu, Oct 23, 2014 at 06:29:14PM -0500, Eric Sandeen wrote:
>> Enable "make C=1" or "make C=2" to do sparse checking.
>> Blatantly ripped off from djwong's patch in e2fsprogs to
>> do the same.
>>
>> Note, this requires unreleased sparse after v0.5, which
>> enables the CHAR_BIT definition; otherwise it chokes.
> 
> I'm pretty sure I used to be able to do sparse checks on xfsprogs using
> 
> CC=cgcc make

Hm, so you can.

Ok, so maybe this is dumb, or is it convenient (to work like it does
in the kernel tree?)

Thanks,
-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-10-24 13:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-23 23:29 [PATCH] xfsprogs: enable sparse checking Eric Sandeen
2014-10-24  6:17 ` Christoph Hellwig
2014-10-24 13:53   ` Eric Sandeen [this message]
2014-10-24 15:40     ` Christoph Hellwig
2014-10-24 15:48       ` Eric Sandeen
2014-10-27  9:48         ` Christoph Hellwig
2014-10-27 13:25           ` Eric Sandeen
2014-10-27 18:50 ` Eric Sandeen

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=544A59F7.4070601@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=hch@infradead.org \
    --cc=sandeen@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.