From: Peter Zijlstra <peterz@infradead.org>
To: Joe Perches <joe@perches.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Anshul Garg <aksgarg1989@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>, Will Deacon <will.deacon@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Matthew Wilcox <mawilcox@microsoft.com>,
Kees Cook <keescook@chromium.org>,
Michael Davidson <md@google.com>
Subject: Re: [PATCH -v2 0/3] lib/int_sqrt: Fix optimize and document
Date: Thu, 2 Nov 2017 17:47:24 +0100 [thread overview]
Message-ID: <20171102164724.olgq3nvouibbgw2t@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1509641030.31043.81.camel@perches.com>
On Thu, Nov 02, 2017 at 09:43:50AM -0700, Joe Perches wrote:
> On Fri, 2017-10-20 at 15:31 -0400, Linus Torvalds wrote:
> > On Fri, Oct 20, 2017 at 12:44 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> > > Version with hopefully acceptable Changelogs.
> >
> > Ack.
>
> Still not in -next
I got emails from Andrew's bot.. I have no idea where Andrew keeps his
pile-'o-patches these days, but that'd be the place to check.
next prev parent reply other threads:[~2017-11-02 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 16:44 [PATCH -v2 0/3] lib/int_sqrt: Fix optimize and document Peter Zijlstra
2017-10-20 16:44 ` [PATCH -v2 1/3] lib/int_sqrt: Optimize small argument Peter Zijlstra
2017-10-20 16:44 ` [PATCH -v2 2/3] lib/int_sqrt: Optimize initial value compute Peter Zijlstra
2017-10-20 16:44 ` [PATCH -v2 3/3] lib/int_sqrt: Adjust comments Peter Zijlstra
2017-10-20 19:31 ` [PATCH -v2 0/3] lib/int_sqrt: Fix optimize and document Linus Torvalds
2017-11-02 16:43 ` Joe Perches
2017-11-02 16:47 ` Peter Zijlstra [this message]
2017-11-02 16:51 ` Kees Cook
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=20171102164724.olgq3nvouibbgw2t@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=aksgarg1989@gmail.com \
--cc=dave@stgolabs.net \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mawilcox@microsoft.com \
--cc=md@google.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.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.