From: corbet@lwn.net (Jonathan Corbet)
To: Heikki Orsila <shdl@zakalwe.fi>
Cc: linux-kernel@vger.kernel.org, rdunlap@xenotime.net
Subject: Re: [PATCH] Documentation: improvement to volatile considered harmful (resubmit)
Date: Mon, 02 Jul 2007 08:59:45 -0600 [thread overview]
Message-ID: <15122.1183388385@lwn.net> (raw)
In-Reply-To: Your message of "Sun, 01 Jul 2007 15:26:22 +0300." <20070701122622.GC3400@zakalwe.fi>
Heikki Orsila <shdl@zakalwe.fi> wrote:
> I'm resubmitting this as I didn't get any replies, this time CCeing
> proper people, sorry..
>
> Kernel locking/synchronization primitives are better than volatile types
> from code readability point of view also.
I think that just dilutes the real point. It's not a choice between
locking and volatile - the locking must be there regardless. It's a
correctness issue; if the result happens to be more readable too that's
a bonus.
If somebody wants to put this sentence in I won't object, but I don't
think it really improves the document either.
Thanks,
jon
prev parent reply other threads:[~2007-07-02 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 12:26 [PATCH] Documentation: improvement to volatile considered harmful (resubmit) Heikki Orsila
2007-07-02 14:59 ` Jonathan Corbet [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=15122.1183388385@lwn.net \
--to=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=shdl@zakalwe.fi \
/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