From: Andy Whitcroft <apw@shadowen.org>
To: Roland Dreier <rdreier@cisco.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: scripts/checkpatch.pl refers to non-existent Documentation/Documentation/volatile-considered-harmful.txt
Date: Thu, 21 Jun 2007 09:20:55 +0100 [thread overview]
Message-ID: <467A34E7.1050107@shadowen.org> (raw)
In-Reply-To: <ada3b0m8hr0.fsf@cisco.com>
Roland Dreier wrote:
> Commit 4a0df2ef added the following to scripts/checkpatch.pl:
>
> print "Use of volatile is usually wrong: see Documentation/volatile-considered-harmful.txt\n";
>
> but Linus's tree has no such file. not sure what the right thing to
> do here is, since I assume we do ultimately want something of the sort
> in Documentation...
That is a little unfortuanate for sure. As Jasper correctly indicates
this file is coming soon to a linus tree near you and things will be
accurate. Otherwise it can be obtained from the current -mm tarball.
It can also be found here on LWN:
http://lwn.net/Articles/234017/
-apw
prev parent reply other threads:[~2007-06-21 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 20:59 scripts/checkpatch.pl refers to non-existent Documentation/Documentation/volatile-considered-harmful.txt Roland Dreier
2007-06-20 21:03 ` Jesper Juhl
2007-06-23 4:05 ` Andrew Morton
2007-06-21 8:20 ` Andy Whitcroft [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=467A34E7.1050107@shadowen.org \
--to=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.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.