linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Nicholas Piggin <npiggin@gmail.com>,
	linuxppc-dev@lists.ozlabs.org,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: [PATCH 0/3] latest cpufeatures patch series
Date: Wed,  5 Apr 2017 22:37:03 +1000	[thread overview]
Message-ID: <20170405123706.6081-1-npiggin@gmail.com> (raw)

Hi,

This is the latest cpufeatures series for Linux. It should be
close to merge now I hope, but another round of review would
be good.

If we can merge the first minor patches and get those out of
the way it would be helpful.

Thanks,
Nick

             reply	other threads:[~2017-04-05 12:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05 12:37 Nicholas Piggin [this message]
2017-04-05 12:37 ` [PATCH 1/3] powerpc/64s: POWER9 no LPCR VRMASD bits Nicholas Piggin
2017-04-05 12:37 ` [PATCH 2/3] of/fdt: introduce of_scan_flat_dt_subnodes and of_get_flat_dt_phandle Nicholas Piggin
     [not found]   ` <CAL_JsqK4zbACwWVb-rsrvBb4hjBCexrqKRKrzSiZrZH5w=bKqQ@mail.gmail.com>
     [not found]     ` <20170406003251.533e2845@roar.ozlabs.ibm.com>
2017-04-05 15:58       ` Rob Herring
2017-04-05 20:58         ` Benjamin Herrenschmidt
2017-04-06  0:38           ` Nicholas Piggin
2017-04-06 14:09             ` Rob Herring
2017-04-10  5:43               ` Nicholas Piggin
2017-04-10 13:42                 ` Rob Herring
2017-04-07  6:40         ` Michael Ellerman
2017-04-05 12:37 ` [PATCH 3/3] powerpc/64s: cpufeatures: add initial implementation for cpufeatures Nicholas Piggin
2017-04-06  8:59   ` kbuild test robot
2017-04-10  7:21   ` 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=20170405123706.6081-1-npiggin@gmail.com \
    --to=npiggin@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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;
as well as URLs for NNTP newsgroup(s).