public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Hans-Christian Egtvedt <egtvedt@samfundet.no>
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org, peterz@infradead.org,
	paulmck@linux.vnet.ibm.com, hskinnemoen@gmail.com,
	tglx@linutronix.de, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:locking/core] arch,avr32: Convert smp_mb__*()
Date: Tue, 22 Apr 2014 07:03:36 +0200	[thread overview]
Message-ID: <20140422050336.GA7784@gmail.com> (raw)
In-Reply-To: <20140421192822.GA29890@samfundet.no>


* Hans-Christian Egtvedt <egtvedt@samfundet.no> wrote:

> Around Fri 18 Apr 2014 06:05:23 -0700 or thereabout, tip-bot for Peter Zijlstra wrote:
> > Commit-ID:  710adaa913169d7183cdf0de41c2a349101ff615
> > Gitweb:     http://git.kernel.org/tip/710adaa913169d7183cdf0de41c2a349101ff615
> > Author:     Peter Zijlstra <peterz@infradead.org>
> > AuthorDate: Thu, 13 Mar 2014 19:00:37 +0100
> > Committer:  Ingo Molnar <mingo@kernel.org>
> > CommitDate: Fri, 18 Apr 2014 11:40:33 +0200
> > 
> > arch,avr32: Convert smp_mb__*()
> > 
> > AVR32's mb() implementation is a compiler barrier(), therefore it all
> > doesn't matter, fully rely on whatever asm-generic/barrier.h
> > generates.
> 
> Thanks for cleaning, would this go in through some tip-tree? Or would you
> prefer if I added it to my for-linus branch?

Yeah, the plan would be for this to go via the locking tree 
(tip:locking/core), for v3.16 - together with similar patches for 
other architectures.

Thanks,

	Ingo

      reply	other threads:[~2014-04-22  5:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-18 13:05 [tip:locking/core] arch,avr32: Convert smp_mb__*() tip-bot for Peter Zijlstra
2014-04-21 19:28 ` Hans-Christian Egtvedt
2014-04-22  5:03   ` Ingo Molnar [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=20140422050336.GA7784@gmail.com \
    --to=mingo@kernel.org \
    --cc=egtvedt@samfundet.no \
    --cc=hpa@zytor.com \
    --cc=hskinnemoen@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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