From: Leonardo Bras <leonardo@linux.ibm.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Bharata B Rao <bharata.rao@in.ibm.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Bharata B Rao <bharata@linux.ibm.com>
Subject: Re: [PATCH v3 1/1] ppc/spapr: Add hotremovable flag on DIMM LMBs on drmem_v2
Date: Thu, 02 Apr 2020 20:19:34 -0300 [thread overview]
Message-ID: <2cf25efdae30ea7a728c1a1e62e41c65f9073d5c.camel@linux.ibm.com> (raw)
In-Reply-To: <20200402231645.GT47772@umbus.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
On Fri, 2020-04-03 at 10:16 +1100, David Gibson wrote:
> On Thu, Apr 02, 2020 at 08:00:57PM -0300, Leonardo Bras wrote:
> > Hello David,
> >
> > On Fri, 2020-04-03 at 09:49 +1100, David Gibson wrote:
> > > The change looks reasonable. Is there a PAPR RFC I can see describing
> > > the new bit, though?
> >
> > The ACR is approved and I already added the change to LoPAPR/LOPAR,
> > it's just a matter of time to get it released.
> > (I think it's accessible to members of OpenPower Foundation)
>
> Hrm. The latest LoPAPR I can find is from 2016, so a "matter of time"
> isn't very encouraging.
I understand the feeling.
There is a new initiative inside the OpenPower Foundation to keep these
documents updated.
I think we will be able to have more frequent updates of the
documentation soon.
Best Regards,
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-04-02 23:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 17:23 [PATCH v3 1/1] ppc/spapr: Add hotremovable flag on DIMM LMBs on drmem_v2 Leonardo Bras
2020-04-02 22:49 ` David Gibson
2020-04-02 23:00 ` Leonardo Bras
2020-04-02 23:16 ` David Gibson
2020-04-02 23:19 ` Leonardo Bras [this message]
2020-04-02 23:40 ` David Gibson
2020-04-03 0:00 ` Leonardo Bras
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=2cf25efdae30ea7a728c1a1e62e41c65f9073d5c.camel@linux.ibm.com \
--to=leonardo@linux.ibm.com \
--cc=bharata.rao@in.ibm.com \
--cc=bharata@linux.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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 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).