public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: enable sparse endianess checking by default?
Date: Thu, 25 Sep 2014 08:52:52 -0700	[thread overview]
Message-ID: <20140925155252.GA5720@infradead.org> (raw)

It's been quite a while that we had sparse support in the build system,
and we still disable the checks for endianess annotations by default.

For many subsystems these are arguably the most useful ones, and with
Fengguang's build bot running sparse checks we're also being harder
on driver maintainers to sort these out even where they don't matter
too much for them (e.g. PCI hardware that mostly runs on x86).

Is there any reason to still keep the opt-in for these when running
sparse?

Now running sparse by default if available would be another useful
project, but I'll save that for a later time..

                 reply	other threads:[~2014-09-25 15:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140925155252.GA5720@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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