From: Nicholas Piggin <npiggin@gmail.com>
To: Christoph Lameter <cl@linux.com>
Cc: Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] percpu: improve generic percpu modify-return implementation
Date: Thu, 22 Sep 2016 14:42:56 +1000 [thread overview]
Message-ID: <20160922144256.1b9d98c6@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1609211514440.18800@east.gentwo.org>
On Wed, 21 Sep 2016 15:16:25 -0500 (CDT)
Christoph Lameter <cl@linux.com> wrote:
> On Wed, 21 Sep 2016, Tejun Heo wrote:
>
> > Hello, Nick.
> >
> > How have you been? :)
> >
>
> He is baack. Are we getting SL!B? ;-)
>
Hey Christoph. Sure, why not.
WARNING: multiple messages have this Message-ID (diff)
From: Nicholas Piggin <npiggin@gmail.com>
To: Christoph Lameter <cl@linux.com>
Cc: Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] percpu: improve generic percpu modify-return implementation
Date: Thu, 22 Sep 2016 14:42:56 +1000 [thread overview]
Message-ID: <20160922144256.1b9d98c6@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1609211514440.18800@east.gentwo.org>
On Wed, 21 Sep 2016 15:16:25 -0500 (CDT)
Christoph Lameter <cl@linux.com> wrote:
> On Wed, 21 Sep 2016, Tejun Heo wrote:
>
> > Hello, Nick.
> >
> > How have you been? :)
> >
>
> He is baack. Are we getting SL!B? ;-)
>
Hey Christoph. Sure, why not.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-09-22 4:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 8:51 [PATCH] percpu: improve generic percpu modify-return implementation Nicholas Piggin
2016-09-21 10:25 ` kbuild test robot
2016-09-21 10:25 ` kbuild test robot
2016-09-21 10:25 ` kbuild test robot
2016-09-21 10:30 ` kbuild test robot
2016-09-21 10:30 ` kbuild test robot
2016-09-21 10:30 ` kbuild test robot
2016-09-21 10:30 ` kbuild test robot
2016-09-21 10:30 ` kbuild test robot
2016-09-21 10:30 ` kbuild test robot
2016-09-21 10:57 ` Nicholas Piggin
2016-09-21 10:57 ` Nicholas Piggin
2016-09-21 10:57 ` Nicholas Piggin
2016-09-21 14:23 ` Tejun Heo
2016-09-21 20:16 ` Christoph Lameter
2016-09-21 20:16 ` Christoph Lameter
2016-09-22 4:42 ` Nicholas Piggin [this message]
2016-09-22 4:42 ` Nicholas Piggin
2016-09-22 4:35 ` Nicholas Piggin
2016-09-22 4:35 ` Nicholas Piggin
2016-09-22 4:35 ` Nicholas Piggin
2016-09-22 4:35 ` Nicholas Piggin
2016-09-22 16:07 ` Tejun Heo
2016-09-23 7:33 ` Nicholas Piggin
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=20160922144256.1b9d98c6@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=cl@linux.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tj@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.