From: Peter Fritzsche <Peter.Fritzsche@gmx.de>
To: Jamie Lokier <jamie@shareable.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Arnd Bergmann <arnd@arndb.de>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
Keith M Wesolowski <wesolows@foobazco.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [PATCH 2/2] asm-generic: Don't warn that atomic_t is only 24 bit
Date: Wed, 28 Apr 2010 20:42:09 +0200 [thread overview]
Message-ID: <201004282042.15485.Peter.Fritzsche@gmx.de> (raw)
In-Reply-To: <20100428152815.GB25569@shareable.org>
On Wednesday 28 April 2010 17:28:15 you wrote:
> If the comment's getting removed, it should probably go from here too:
>
> linux-2.6$ git grep '24' arch/*/include/*/atomic*
> arch/mn10300/include/asm/atomic.h: * useful range of an atomic_t is only 24
> bits arch/mn10300/include/asm/atomic.h: * useful range of an atomic_t is
> only 24 bits arch/mn10300/include/asm/atomic.h: * Note that the guaranteed
> useful range of an arch/mn10300/include/asm/atomic.h: * Note that the
> guaranteed useful range of an
This is part one of the patch - already sent to the mn10300 people. Currently
only got Acked reponses for both patches
Best regards,
Peter Fritzsche
next prev parent reply other threads:[~2010-04-28 18:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 10:50 [PATCH 1/2] mn10300: Don't warn that atomic_t is only 24 bit Peter Fritzsche
2010-04-28 11:10 ` [PATCH 2/2] asm-generic: " Peter Fritzsche
2010-04-28 11:10 ` Peter Fritzsche
2010-04-28 13:33 ` Arnd Bergmann
2010-04-28 13:54 ` Mathieu Desnoyers
2010-04-28 15:28 ` Jamie Lokier
2010-04-28 16:27 ` Mathieu Desnoyers
2010-04-29 16:22 ` David Howells
2010-04-29 21:10 ` Mathieu Desnoyers
2010-04-30 8:53 ` Peter Fritzsche
2010-04-28 18:42 ` Peter Fritzsche [this message]
2010-04-28 16:46 ` David Miller
2010-04-28 13:22 ` [PATCH 1/2] mn10300: " David Howells
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=201004282042.15485.Peter.Fritzsche@gmx.de \
--to=peter.fritzsche@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=heiko.carstens@de.ibm.com \
--cc=jamie@shareable.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=schwidefsky@de.ibm.com \
--cc=wesolows@foobazco.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 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.