All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: rafael@kernel.org, bp@suse.de, lenb@kernel.org,
	james.morse@arm.com, tony.luck@intel.com, bp@alien8.de,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] apei/ghes: remove unused ghes_estatus_pool_size_request
Date: Mon, 5 Jun 2023 19:14:29 +0200	[thread overview]
Message-ID: <CAJZ5v0gQS6O0Gj3vd-xdqEV+vpbCVg1Mdq8r-W0ZXpsKHyyRFA@mail.gmail.com> (raw)
In-Reply-To: <20230527095158.211568-1-linmiaohe@huawei.com>

On Sat, May 27, 2023 at 4:00 AM Miaohe Lin <linmiaohe@huawei.com> wrote:
>
> ghes_estatus_pool_size_request is unused now. Remove it.
>
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>

Applied as 6.5 material, thanks!

> ---
>  drivers/acpi/apei/ghes.c | 2 --
>  1 file changed, 2 deletions(-)
>
> diff --git a/drivers/acpi/apei/ghes.c b/drivers/acpi/apei/ghes.c
> index 34ad071a64e9..a4148a7d3afe 100644
> --- a/drivers/acpi/apei/ghes.c
> +++ b/drivers/acpi/apei/ghes.c
> @@ -152,7 +152,6 @@ struct ghes_vendor_record_entry {
>  };
>
>  static struct gen_pool *ghes_estatus_pool;
> -static unsigned long ghes_estatus_pool_size_request;
>
>  static struct ghes_estatus_cache __rcu *ghes_estatus_caches[GHES_ESTATUS_CACHES_SIZE];
>  static atomic_t ghes_estatus_cache_alloced;
> @@ -191,7 +190,6 @@ int ghes_estatus_pool_init(unsigned int num_ghes)
>         len = GHES_ESTATUS_CACHE_AVG_SIZE * GHES_ESTATUS_CACHE_ALLOCED_MAX;
>         len += (num_ghes * GHES_ESOURCE_PREALLOC_MAX_SIZE);
>
> -       ghes_estatus_pool_size_request = PAGE_ALIGN(len);
>         addr = (unsigned long)vmalloc(PAGE_ALIGN(len));
>         if (!addr)
>                 goto err_pool_alloc;
> --
> 2.27.0
>

      reply	other threads:[~2023-06-05 17:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-27  9:51 [PATCH] apei/ghes: remove unused ghes_estatus_pool_size_request Miaohe Lin
2023-06-05 17:14 ` 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=CAJZ5v0gQS6O0Gj3vd-xdqEV+vpbCVg1Mdq8r-W0ZXpsKHyyRFA@mail.gmail.com \
    --to=rafael@kernel.org \
    --cc=bp@alien8.de \
    --cc=bp@suse.de \
    --cc=james.morse@arm.com \
    --cc=lenb@kernel.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.