Linux-ACPI Archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Chen Yu <yu.c.chen@intel.com>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	linux-acpi@vger.kernel.org,  acpica-devel@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI: tools: pfrut: Print the update_cap field during capability query
Date: Fri, 26 Apr 2024 19:29:39 +0200	[thread overview]
Message-ID: <CAJZ5v0i5XhOzLr+9yrjzgM+GntFHFW+pQGV6EnHfNEoatXjjOg@mail.gmail.com> (raw)
In-Reply-To: <20240426094850.757123-1-yu.c.chen@intel.com>

On Fri, Apr 26, 2024 at 11:50 AM Chen Yu <yu.c.chen@intel.com> wrote:
>
> There is request from the end user to print this field to better
> query what type of update capability is supported on this platform.
>
> Signed-off-by: Chen Yu <yu.c.chen@intel.com>
> ---
>  tools/power/acpi/tools/pfrut/pfrut.c | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/tools/power/acpi/tools/pfrut/pfrut.c b/tools/power/acpi/tools/pfrut/pfrut.c
> index 388c9e3ad040..44a9ecbd91e8 100644
> --- a/tools/power/acpi/tools/pfrut/pfrut.c
> +++ b/tools/power/acpi/tools/pfrut/pfrut.c
> @@ -174,6 +174,8 @@ void print_cap(struct pfru_update_cap_info *cap)
>                 exit(1);
>         }
>
> +       printf("update capability:%d\n", cap->update_cap);
> +
>         uuid_unparse(cap->code_type, uuid);
>         printf("code injection image type:%s\n", uuid);
>         printf("fw_version:%d\n", cap->fw_version);
> --

Applied as 6.10 material, thanks!

      reply	other threads:[~2024-04-26 17:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-26  9:48 [PATCH] ACPI: tools: pfrut: Print the update_cap field during capability query Chen Yu
2024-04-26 17:29 ` Rafael J. Wysocki [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=CAJZ5v0i5XhOzLr+9yrjzgM+GntFHFW+pQGV6EnHfNEoatXjjOg@mail.gmail.com \
    --to=rafael@kernel.org \
    --cc=acpica-devel@lists.linux.dev \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=yu.c.chen@intel.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 read-only IMAP folder(s) and NNTP newsgroup(s).