From: David Hildenbrand <david@redhat.com>
To: Gavin Shan <gshan@redhat.com>, linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, osalvador@suse.de,
gregkh@linuxfoundation.org, rafael@kernel.org, dakr@kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH 2/2] drivers/base/memory: Correct the field name in the header
Date: Fri, 14 Feb 2025 08:54:48 +0100 [thread overview]
Message-ID: <4df20b47-bf32-4772-8c71-2d7d46f370e5@redhat.com> (raw)
In-Reply-To: <20250214063504.617906-3-gshan@redhat.com>
On 14.02.25 07:35, Gavin Shan wrote:
> Replace @blocks with @memory_blocks to match with the definition
> of struct memory_group.
>
> Signed-off-by: Gavin Shan <gshan@redhat.com>
> ---
> include/linux/memory.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/memory.h b/include/linux/memory.h
> index c0afee5d126e..12daa6ec7d09 100644
> --- a/include/linux/memory.h
> +++ b/include/linux/memory.h
> @@ -25,7 +25,7 @@
> /**
> * struct memory_group - a logical group of memory blocks
> * @nid: The node id for all memory blocks inside the memory group.
> - * @blocks: List of all memory blocks belonging to this memory group.
> + * @memory_blocks: List of all memory blocks belonging to this memory group.
> * @present_kernel_pages: Present (online) memory outside ZONE_MOVABLE of this
> * memory group.
> * @present_movable_pages: Present (online) memory in ZONE_MOVABLE of this
Acked-by: David Hildenbrand <david@redhat.com>
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2025-02-14 7:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 6:35 [PATCH 0/2] drivers/base/memory: Two cleanups Gavin Shan
2025-02-14 6:35 ` [PATCH 1/2] drivers/base/memory: Simplify add_boot_memory_block() Gavin Shan
2025-02-14 7:53 ` David Hildenbrand
2025-02-14 23:48 ` Gavin Shan
2025-02-14 22:57 ` Andrew Morton
2025-02-14 23:45 ` Gavin Shan
2025-02-14 6:35 ` [PATCH 2/2] drivers/base/memory: Correct the field name in the header Gavin Shan
2025-02-14 7:54 ` David Hildenbrand [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=4df20b47-bf32-4772-8c71-2d7d46f370e5@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=gshan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=rafael@kernel.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
all inboxes | Powered by JetHome®