From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Boqun Feng <boqun.feng@gmail.com>,
Michael Ellerman <mpe@ellerman.id.au>,
linux-arch@vger.kernel.org,
Christophe Leroy <christophe.leroy@c-s.fr>,
Will Deacon <will@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] powerpc: convert to use ARCH_ATOMIC
Date: Tue, 15 Dec 2020 22:01:53 +1100 (AEDT) [thread overview]
Message-ID: <160803006828.517022.11653746040201770780.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20201111110723.3148665-1-npiggin@gmail.com>
On Wed, 11 Nov 2020 21:07:20 +1000, Nicholas Piggin wrote:
> This conversion seems to require generic atomic64 changes, looks
> like nothing else uses ARCH_ATOMIC and GENERIC_ATOMIC64 yet.
>
> Thanks,
> Nick
>
> Nicholas Piggin (3):
> asm-generic/atomic64: Add support for ARCH_ATOMIC
> powerpc/64s/iommu: don't use atomic_ function on atomic64_t type
> powerpc: rewrite atomics to use ARCH_ATOMIC
>
> [...]
Patch 2 applied to powerpc/next.
[2/3] powerpc/64s/iommu: Don't use atomic_ function on atomic64_t type
https://git.kernel.org/powerpc/c/c33cd1ed60013ec2ae50f91fed260def5f1d9851
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: Christophe Leroy <christophe.leroy@c-s.fr>,
linux-arch@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
Boqun Feng <boqun.feng@gmail.com>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH 0/3] powerpc: convert to use ARCH_ATOMIC
Date: Tue, 15 Dec 2020 22:01:53 +1100 (AEDT) [thread overview]
Message-ID: <160803006828.517022.11653746040201770780.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20201111110723.3148665-1-npiggin@gmail.com>
On Wed, 11 Nov 2020 21:07:20 +1000, Nicholas Piggin wrote:
> This conversion seems to require generic atomic64 changes, looks
> like nothing else uses ARCH_ATOMIC and GENERIC_ATOMIC64 yet.
>
> Thanks,
> Nick
>
> Nicholas Piggin (3):
> asm-generic/atomic64: Add support for ARCH_ATOMIC
> powerpc/64s/iommu: don't use atomic_ function on atomic64_t type
> powerpc: rewrite atomics to use ARCH_ATOMIC
>
> [...]
Patch 2 applied to powerpc/next.
[2/3] powerpc/64s/iommu: Don't use atomic_ function on atomic64_t type
https://git.kernel.org/powerpc/c/c33cd1ed60013ec2ae50f91fed260def5f1d9851
cheers
next prev parent reply other threads:[~2020-12-15 11:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 11:07 [PATCH 0/3] powerpc: convert to use ARCH_ATOMIC Nicholas Piggin
2020-11-11 11:07 ` Nicholas Piggin
2020-11-11 11:07 ` [PATCH 1/3] asm-generic/atomic64: Add support for ARCH_ATOMIC Nicholas Piggin
2020-11-11 11:07 ` Nicholas Piggin
2020-11-11 13:39 ` Christophe Leroy
2020-11-11 13:39 ` Christophe Leroy
2020-11-11 13:44 ` Peter Zijlstra
2020-11-11 13:44 ` Peter Zijlstra
2020-11-16 1:48 ` Nicholas Piggin
2020-11-16 1:48 ` Nicholas Piggin
2020-11-11 11:07 ` [PATCH 2/3] powerpc/64s/iommu: don't use atomic_ function on atomic64_t type Nicholas Piggin
2020-11-11 11:07 ` Nicholas Piggin
2020-11-11 11:07 ` [PATCH 3/3] powerpc: rewrite atomics to use ARCH_ATOMIC Nicholas Piggin
2020-11-11 11:07 ` Nicholas Piggin
2020-11-11 19:07 ` kernel test robot
2020-11-11 19:07 ` kernel test robot
2020-11-11 19:07 ` kernel test robot
2020-11-13 5:05 ` kernel test robot
2020-11-13 5:05 ` kernel test robot
2020-11-13 5:05 ` kernel test robot
2020-11-13 15:30 ` Boqun Feng
2020-11-13 15:30 ` Boqun Feng
2020-12-22 3:52 ` Nicholas Piggin
2020-12-22 3:52 ` Nicholas Piggin
2020-12-23 2:45 ` Boqun Feng
2020-12-23 2:45 ` Boqun Feng
2020-12-15 11:01 ` Michael Ellerman [this message]
2020-12-15 11:01 ` [PATCH 0/3] powerpc: convert " Michael Ellerman
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=160803006828.517022.11653746040201770780.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=aik@ozlabs.ru \
--cc=arnd@arndb.de \
--cc=boqun.feng@gmail.com \
--cc=christophe.leroy@c-s.fr \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=will@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 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.