From: Tilman Schmidt <tilman@imap.cc>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Karsten Keil <kkeil@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
i4ldeveloper@listserv.isdn4linux.de,
linux-serial@vger.kernel.org, Hansjoerg Lipp <hjlipp@web.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Greg KH <greg@kroah.com>
Subject: Re: [PATCH] drivers/isdn/gigaset: new M101 driver
Date: Mon, 05 Feb 2007 13:29:20 +0100 [thread overview]
Message-ID: <45C72320.5040103@imap.cc> (raw)
In-Reply-To: <20070204205817.fe686375.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]
Andrew Morton schrieb:
> On Mon, 05 Feb 2007 02:42:09 +0100 Tilman Schmidt <tilman@imap.cc> wrote:
>
>> It's a pointer. Are reads and writes of pointer sized objects
>> guaranteed to be atomic on every platform?
>
> Yup - we make the same assumption about longs in various places.
>
> It's a bit strange to read a pointer which can be changing at the
> same time. Because the local copy will no longer represent the
> thing which it was just copied from.
It's not that bad. The only possible concurrent change is from NULL
to non-NULL. Fearing an inconsistent read in that event was too
paranoid apparently.
Thanks for all your suggestions. I'll prepare a new patch based on
them.
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
prev parent reply other threads:[~2007-02-05 12:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 21:12 [PATCH] drivers/isdn/gigaset: new M101 driver Tilman Schmidt
2007-02-02 1:13 ` Andrew Morton
2007-02-03 16:09 ` Greg KH
2007-02-04 0:26 ` Tilman Schmidt
2007-02-12 18:47 ` Greg KH
2007-02-12 23:49 ` Tilman Schmidt
2007-02-04 1:32 ` Tilman Schmidt
2007-02-04 1:56 ` Andrew Morton
2007-02-05 1:42 ` Tilman Schmidt
2007-02-05 4:58 ` Andrew Morton
2007-02-05 12:29 ` Tilman Schmidt [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=45C72320.5040103@imap.cc \
--to=tilman@imap.cc \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=hjlipp@web.de \
--cc=i4ldeveloper@listserv.isdn4linux.de \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).