linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Laurent Dufour <ldufour@linux.ibm.com>,
	linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Cc: Nathan Lynch <nathanl@linux.ibm.com>, tyreld@linux.ibm.com
Subject: Re: [PATCH v5] powerpc/pseries: read the lpar name from the firmware
Date: Tue, 15 Feb 2022 16:26:27 +1100	[thread overview]
Message-ID: <164490278732.270256.5912946204648546254.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20220106161339.74656-1-ldufour@linux.ibm.com>

On Thu, 6 Jan 2022 17:13:39 +0100, Laurent Dufour wrote:
> The LPAR name may be changed after the LPAR has been started in the HMC.
> In that case lparstat command is not reporting the updated value because it
> reads it from the device tree which is read at boot time.
> 
> However this value could be read from RTAS.
> 
> Adding this value in the /proc/powerpc/lparcfg output allows to read the
> updated value.
> 
> [...]

Applied to powerpc/next.

[1/1] powerpc/pseries: read the lpar name from the firmware
      https://git.kernel.org/powerpc/c/eddaa9a402758d379520f6511fb61e89990698aa

cheers

      parent reply	other threads:[~2022-02-15  5:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 16:13 [PATCH v5] powerpc/pseries: read the lpar name from the firmware Laurent Dufour
2022-01-06 21:13 ` Nathan Lynch
2022-01-06 21:38 ` Tyrel Datwyler
2022-01-11 22:40   ` Michael Ellerman
2022-01-12 13:10     ` Laurent Dufour
2022-01-10 13:33 ` kernel test robot
2022-02-15  5:26 ` Michael Ellerman [this message]

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=164490278732.270256.5912946204648546254.b4-ty@ellerman.id.au \
    --to=patch-notifications@ellerman.id.au \
    --cc=ldufour@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nathanl@linux.ibm.com \
    --cc=tyreld@linux.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).