From: Al Viro <viro@ftp.linux.org.uk>
To: Grant Coady <gcoady.lk@gmail.com>
Cc: Neil Brown <neilb@suse.de>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHSET] nfs endianness annotations
Date: Thu, 19 Oct 2006 12:49:00 +0100 [thread overview]
Message-ID: <20061019114900.GS29920@ftp.linux.org.uk> (raw)
In-Reply-To: <du2ej21g7pkccoe4cigs8r9gsq1ir6nc9p@4ax.com>
On Thu, Oct 19, 2006 at 03:30:25PM +1000, Grant Coady wrote:
> On Thu, 19 Oct 2006 02:26:00 +0100, Al Viro <viro@ftp.linux.org.uk> wrote:
>
> >Folks, seriously, please run sparse after changes; it's a simple matter of
> >make C=2 CF=-D__CHECK_ENDIAN__ fs/nfs*/; nothing tricky and it saves a lot
> >of potential PITA...
>
> grant@sempro:~/linux/linux-2.6.19-rc2a$ make C=2 CF=-D__CHECK_ENDIAN__ fs/nfs*/;
> CHK include/linux/version.h
> CHK include/linux/utsrelease.h
> CHECK scripts/mod/empty.c
> /bin/sh: sparse: command not found
> make[2]: *** [scripts/mod/empty.o] Error 127
> make[1]: *** [scripts/mod] Error 2
> make: *** [scripts] Error 2
>
> What sparse? Pointer please? Hell of a keyword to search for :(
$ grep -l sparse Documentation/*
Documentation/CodingStyle
Documentation/README.DAC960
Documentation/SubmitChecklist
Documentation/sparse.txt
$
next prev parent reply other threads:[~2006-10-19 11:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1GX7zV-00047C-PO@ZenIV.linux.org.uk>
2006-10-18 21:26 ` [PATCHSET] nfs endianness annotations Trond Myklebust
2006-10-19 0:31 ` Neil Brown
2006-10-19 1:26 ` Al Viro
2006-10-19 2:55 ` Neil Brown
2006-10-19 5:30 ` Grant Coady
2006-10-19 6:32 ` Neil Brown
2006-10-19 23:22 ` Randy Dunlap
2006-10-19 11:49 ` Al Viro [this message]
2006-10-10 3:10 Al Viro
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=20061019114900.GS29920@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=gcoady.lk@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=trond.myklebust@fys.uio.no \
/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.