From: Michael Ellerman <mpe@ellerman.id.au>
To: xinhui <xinhui.pan@linux.vnet.ibm.com>,
kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, benh@kernel.crashing.org,
paulus@samba.org, peterz@infradead.org, mingo@redhat.com,
paulmck@linux.vnet.ibm.com, waiman.long@hpe.com,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH v7 6/6] powerpc: pSeries: Add pv-qspinlock build config/make
Date: Thu, 22 Sep 2016 20:31:59 +1000 [thread overview]
Message-ID: <87a8f08bts.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <57E37216.1030505@linux.vnet.ibm.com>
xinhui <xinhui.pan@linux.vnet.ibm.com> writes:
> hi, all
> ok, this patch set depends on
> https://patchwork.kernel.org/patch/8953981/ [V4] powerpc: Implement {cmp}xchg for u8 and u16
AKA: https://patchwork.ozlabs.org/patch/615480/
Sorry I saw the discussion on that and thought there'd be a new version.
But now I read the whole thread it looks like it was OK in the end.
I'll try and get it merged.
cheers
prev parent reply other threads:[~2016-09-22 10:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 9:23 [PATCH v7 0/6] Implement qspinlock/pv-qspinlock on ppc Pan Xinhui
2016-09-19 9:23 ` [PATCH v7 1/6] pv-qspinlock: use cmpxchg_release in __pv_queued_spin_unlock Pan Xinhui
2016-09-22 14:02 ` [tip:locking/core] locking/pv-qspinlock: Use cmpxchg_release() in __pv_queued_spin_unlock() tip-bot for Pan Xinhui
2016-09-19 9:23 ` [PATCH v7 2/6] powerpc/qspinlock: powerpc support qspinlock Pan Xinhui
2016-09-19 9:23 ` [PATCH v7 3/6] powerpc: pseries/Kconfig: Add qspinlock build config Pan Xinhui
2016-09-19 8:40 ` kbuild test robot
2016-09-19 9:23 ` [PATCH v7 4/6] powerpc: lib/locks.c: Add cpu yield/wake helper function Pan Xinhui
2016-09-22 15:17 ` Boqun Feng
2016-09-19 9:23 ` [PATCH v7 5/6] powerpc/pv-qspinlock: powerpc support pv-qspinlock Pan Xinhui
2016-09-19 9:23 ` [PATCH v7 6/6] powerpc: pSeries: Add pv-qspinlock build config/make Pan Xinhui
2016-09-19 8:58 ` kbuild test robot
2016-09-22 5:54 ` xinhui
2016-09-22 10:31 ` Michael Ellerman [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=87a8f08bts.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lkp@intel.com \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=waiman.long@hpe.com \
--cc=xinhui.pan@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox