All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	"rth@twiddle.net" <rth@twiddle.net>,
	"vgupta@synopsys.com" <vgupta@synopsys.com>,
	"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
	"hskinnemoen@gmail.com" <hskinnemoen@gmail.com>,
	"realmz6@gmail.com" <realmz6@gmail.com>,
	"dhowells@redhat.com" <dhowells@redhat.com>,
	"rkuo@codeaurora.org" <rkuo@codeaurora.org>,
	"tony.luck@intel.com" <tony.luck@intel.com>,
	"geert@linux-m68k.org" <geert@linux-m68k.org>,
	"james.hogan@imgtec.com" <james.hogan@imgtec.com>,
	"ralf@linux-mips.org" <ralf@linux-mips.org>,
	"jejb@parisc-linux.org" <jejb@parisc-linux.org>,
	"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
	"heiko.carstens@de.ibm.com" <heiko.carstens@de.ibm.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"cmetcalf@ezchip.com" <cmetcalf@ezchip.com>,
	ysa
Subject: Re: [PATCH 00/28] arch: Provide atomic logic ops
Date: Mon, 27 Jul 2015 12:01:39 +0100	[thread overview]
Message-ID: <20150727110139.GG3358@arm.com> (raw)
In-Reply-To: <20150716172110.587529075@infradead.org>

Hi Peter, Ingo,

On Thu, Jul 16, 2015 at 06:21:10PM +0100, Peter Zijlstra wrote:
> Currently there is an incoherent mess of atomic_{set,clear}_mask() and
> atomic_or() (but no atomic_{and,nand,xor}()) in the tree.
> 
> Those archs that implement atomic_{set,clear}_mask() are not even consistent on
> its signature.
> 
> Implement atomic_{or,and,xor}() on all archs and deprecate
> atomic_{set,clear}_mask().
> 
> The series has been compile tested by the build-bot, no known failures at this time.
> 
> I would like to take this through tip; I'll ask Ingo to put it in a separate
> branch such that people can pull in that branch if there is conflicting work
> elsewhere (Will has some for Argh64).

Any joy with this branch? I'd like to put the new arm64 atomics into
-next, but it would probably be easier for everybody if I merged in this
lot first.

Cheers,

Will

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	"rth@twiddle.net" <rth@twiddle.net>,
	"vgupta@synopsys.com" <vgupta@synopsys.com>,
	"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
	"hskinnemoen@gmail.com" <hskinnemoen@gmail.com>,
	"realmz6@gmail.com" <realmz6@gmail.com>,
	"dhowells@redhat.com" <dhowells@redhat.com>,
	"rkuo@codeaurora.org" <rkuo@codeaurora.org>,
	"tony.luck@intel.com" <tony.luck@intel.com>,
	"geert@linux-m68k.org" <geert@linux-m68k.org>,
	"james.hogan@imgtec.com" <james.hogan@imgtec.com>,
	"ralf@linux-mips.org" <ralf@linux-mips.org>,
	"jejb@parisc-linux.org" <jejb@parisc-linux.org>,
	"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
	"heiko.carstens@de.ibm.com" <heiko.carstens@de.ibm.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"cmetcalf@ezchip.com" <cmetcalf@ezchip.com>,
	"ysato@users.sourceforge.jp" <ysato@users.sourceforge.jp>,
	"mingo@kernel.org" <mingo@kernel.org>
Subject: Re: [PATCH 00/28] arch: Provide atomic logic ops
Date: Mon, 27 Jul 2015 12:01:39 +0100	[thread overview]
Message-ID: <20150727110139.GG3358@arm.com> (raw)
Message-ID: <20150727110139.hi9OBLM98MoqtNqRD4c5u2Js-E3PRcMj-UiK5IUzkbA@z> (raw)
In-Reply-To: <20150716172110.587529075@infradead.org>

Hi Peter, Ingo,

On Thu, Jul 16, 2015 at 06:21:10PM +0100, Peter Zijlstra wrote:
> Currently there is an incoherent mess of atomic_{set,clear}_mask() and
> atomic_or() (but no atomic_{and,nand,xor}()) in the tree.
> 
> Those archs that implement atomic_{set,clear}_mask() are not even consistent on
> its signature.
> 
> Implement atomic_{or,and,xor}() on all archs and deprecate
> atomic_{set,clear}_mask().
> 
> The series has been compile tested by the build-bot, no known failures at this time.
> 
> I would like to take this through tip; I'll ask Ingo to put it in a separate
> branch such that people can pull in that branch if there is conflicting work
> elsewhere (Will has some for Argh64).

Any joy with this branch? I'd like to put the new arm64 atomics into
-next, but it would probably be easier for everybody if I merged in this
lot first.

Cheers,

Will

  parent reply	other threads:[~2015-07-27 11:01 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16 17:21 [PATCH 00/28] arch: Provide atomic logic ops Peter Zijlstra
2015-07-16 17:21 ` [PATCH 01/28] atomic: Prepare generic atomic implementation for " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 02/28] alpha: Provide atomic_{or,xor,and} Peter Zijlstra
2015-07-16 17:21 ` [PATCH 03/28] arc: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 04/28] arm: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 05/28] arm64: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 06/28] avr32: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 07/28] blackfin: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 08/28] hexagon: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 09/28] ia64: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 10/28] m32r: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 11/28] m68k: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 12/28] metag: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 13/28] mips: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 14/28] mn10300: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 15/28] parisc: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 16/28] powerpc: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 17/28] sh: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 18/28] sparc: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 19/28] xtensa: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 20/28] s390: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 21/28] x86: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 22/28] frv: Rewrite atomic implementation Peter Zijlstra
2015-07-16 17:21 ` [PATCH 23/28] h8300: Provide atomic_{or,xor,and} Peter Zijlstra
2015-07-16 17:21 ` [PATCH 24/28] tile: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 25/28] atomic: " Peter Zijlstra
2015-07-16 17:21 ` [PATCH 26/28] atomic: Collapse all atomic_{set,clear}_mask definitions Peter Zijlstra
2015-07-16 17:21 ` [PATCH 27/28] atomic: Replace atomic_{set,clear}_mask() usage Peter Zijlstra
2015-07-16 17:21 ` [PATCH 28/28] atomic: Add simple atomic_t tests Peter Zijlstra
2015-07-17 12:57 ` [PATCH 00/28] arch: Provide atomic logic ops Will Deacon
2015-07-17 12:57   ` Will Deacon
2015-07-21 21:13 ` rkuo
2015-07-27 11:01 ` Will Deacon [this message]
2015-07-27 11:01   ` Will Deacon

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=20150727110139.GG3358@arm.com \
    --to=will.deacon@arm.com \
    --cc=benh@kernel.crashing.org \
    --cc=cmetcalf@ezchip.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=hskinnemoen@gmail.com \
    --cc=james.hogan@imgtec.com \
    --cc=jejb@parisc-linux.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=peterz@infradead.org \
    --cc=ralf@linux-mips.org \
    --cc=realmz6@gmail.com \
    --cc=rkuo@codeaurora.org \
    --cc=rth@twiddle.net \
    --cc=tony.luck@intel.com \
    --cc=vgupta@synopsys.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 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.