linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Bringmann <mwb@linux.vnet.ibm.com>,
	linuxppc-dev@lists.ozlabs.org
Cc: nfont@linux.vnet.ibm.com, Michael Bringmann <mwb@linux.vnet.ibm.com>
Subject: Re: [V6, 1/4] powerpc/firmware: Add definitions for new drc-info firmware feature
Date: Mon, 22 Jan 2018 14:34:13 +1100 (AEDT)	[thread overview]
Message-ID: <3zPxqp1y4wz9sNc@ozlabs.org> (raw)
In-Reply-To: <1d7f84eb-defc-a1ae-fd8b-d4c00a16aedb@linux.vnet.ibm.com>

On Fri, 2017-12-01 at 23:19:40 UTC, Michael Bringmann wrote:
> Firmware Features: Define new bit flag representing the presence of
> new device tree property "ibm,drc-info".  The flag is used to tell
> the front end processor whether the Linux kernel supports the new
> property, and by the front end processor to tell the Linux kernel
> that the new property is present in the device tree.
> 
> Signed-off-by: Michael Bringmann <mwb@linux.vnet.ibm.com>

Series applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/3f38000eda485f466153d37c4f9201

cheers

  reply	other threads:[~2018-01-22  3:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01 23:18 [PATCH V6 0/4] powerpc/devtree: Add support for 'ibm,drc-info' property Michael Bringmann
2017-12-01 23:19 ` [PATCH V6 1/4] powerpc/firmware: Add definitions for new drc-info firmware feature Michael Bringmann
2018-01-22  3:34   ` Michael Ellerman [this message]
2017-12-01 23:19 ` [PATCH V6 2/4] pseries/drc-info: Search DRC properties for CPU indexes Michael Bringmann
2017-12-01 23:19 ` [PATCH V6 3/4] hotplug/drc-info: Add code to search ibm,drc-info property Michael Bringmann
2017-12-01 23:19 ` [PATCH V6 4/4] powerpc: Enable support for ibm,drc-info devtree property Michael Bringmann

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=3zPxqp1y4wz9sNc@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mwb@linux.vnet.ibm.com \
    --cc=nfont@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;
as well as URLs for NNTP newsgroup(s).