From: Paul Jackson <pj@sgi.com>
To: Luke Yang <luke.adi@gmail.com>
Cc: akpm@osdl.org, greg@kroah.com, bunk@stusta.de,
linux-kernel@vger.kernel.org
Subject: Re: ADI Blackfin patch for kernel 2.6.14
Date: Tue, 15 Nov 2005 22:11:46 -0800 [thread overview]
Message-ID: <20051115221146.4487657f.pj@sgi.com> (raw)
In-Reply-To: <489ecd0c0511151944r1552bae3oed5ee88a49795482@mail.gmail.com>
Luke wrote:
> > Cow. You know that volatile in-kernel is basically always wrong?
> >
> I really don't know that... Could you refer me to any document or
> posts talking about it? thank you!
Start with:
http://lkml.org/lkml/2004/1/6/139
> Date Tue, 6 Jan 2004 10:02:18 -0800 (PST)
> From Linus Torvalds <>
> Subject Re: [PATCH] fix get_jiffies_64 to work on voyager
>
> [ This is a big rant against using "volatile" on data structures. Feel
> free to ignore it, but the fact is, I'm right. You should never EVER use
> "volatile" on a data structure. ]
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2005-11-16 6:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 9:28 ADI Blackfin patch for kernel 2.6.14 Luke Yang
2005-11-01 16:51 ` Adrian Bunk
2005-11-02 7:06 ` Luke Yang
2005-11-04 4:59 ` Luke Yang
2005-11-04 23:06 ` Greg KH
2005-11-07 6:58 ` Luke Yang
2005-11-07 16:59 ` Greg KH
2005-11-08 7:50 ` Andrew Morton
2005-11-11 11:26 ` Luke Yang
2005-11-12 11:58 ` Andrey Volkov
2005-11-14 7:22 ` Luke Yang
2005-11-12 21:47 ` Greg KH
2005-11-13 14:22 ` Bernd Schmidt
2005-11-14 7:34 ` Luke Yang
2005-11-14 7:52 ` Arjan van de Ven
2005-11-15 2:40 ` Luke Yang
2005-11-15 4:14 ` Greg KH
2005-11-14 12:53 ` Alan Cox
2005-11-16 3:44 ` Luke Yang
2005-11-16 6:11 ` Paul Jackson [this message]
2005-11-16 6:34 ` Luke Yang
2005-11-16 13:42 ` Bernd Schmidt
-- strict thread matches above, loose matches on Subject: below --
2005-11-14 20:53 Robin Getz
2005-11-15 19:11 ` Matthieu CASTET
2005-11-17 5:38 Robin Getz
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=20051115221146.4487657f.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke.adi@gmail.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