From: Mike Rapoport <rppt@linux.vnet.ibm.com> To: Jonathan Corbet <corbet@lwn.net> Cc: Randy Dunlap <rdunlap@infradead.org>, linux-doc <linux-doc@vger.kernel.org>, linux-mm <linux-mm@kvack.org>, lkml <linux-kernel@vger.kernel.org>, Mike Rapoport <rppt@linux.vnet.ibm.com> Subject: [PATCH v2 08/11] docs/mm: memblock: add kernel-doc comments for memblock_add[_node] Date: Sat, 30 Jun 2018 17:55:03 +0300 [thread overview] Message-ID: <1530370506-21751-9-git-send-email-rppt@linux.vnet.ibm.com> (raw) In-Reply-To: <1530370506-21751-1-git-send-email-rppt@linux.vnet.ibm.com> Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com> --- mm/memblock.c | 27 +++++++++++++++++++++++++-- 1 file changed, 25 insertions(+), 2 deletions(-) diff --git a/mm/memblock.c b/mm/memblock.c index 8159869..3e6be01 100644 --- a/mm/memblock.c +++ b/mm/memblock.c @@ -595,12 +595,35 @@ int __init_memblock memblock_add_range(struct memblock_type *type, } } +/** + * memblock_add_node - add new memblock region within a NUMA node + * @base: base address of the new region + * @size: size of the new region + * @nid: nid of the new region + * + * Add new memblock region [@base, @base + @size) to the "memory" + * type. See memblock_add_range() description for mode details + * + * Return: + * 0 on success, -errno on failure. + */ int __init_memblock memblock_add_node(phys_addr_t base, phys_addr_t size, int nid) { return memblock_add_range(&memblock.memory, base, size, nid, 0); } +/** + * memblock_add - add new memblock region + * @base: base address of the new region + * @size: size of the new region + * + * Add new memblock region [@base, @base + @size) to the "memory" + * type. See memblock_add_range() description for mode details + * + * Return: + * 0 on success, -errno on failure. + */ int __init_memblock memblock_add(phys_addr_t base, phys_addr_t size) { phys_addr_t end = base + size - 1; @@ -1464,9 +1487,9 @@ void __init __memblock_free_early(phys_addr_t base, phys_addr_t size) memblock_remove_range(&memblock.reserved, base, size); } -/* +/** * __memblock_free_late - free bootmem block pages directly to buddy allocator - * @addr: phys starting address of the boot memory block + * @base: phys starting address of the boot memory block * @size: size of the boot memory block in bytes * * This is only useful when the bootmem allocator has already been torn -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Mike Rapoport <rppt@linux.vnet.ibm.com> To: Jonathan Corbet <corbet@lwn.net> Cc: Randy Dunlap <rdunlap@infradead.org>, linux-doc <linux-doc@vger.kernel.org>, linux-mm <linux-mm@kvack.org>, lkml <linux-kernel@vger.kernel.org>, Mike Rapoport <rppt@linux.vnet.ibm.com> Subject: [PATCH v2 08/11] docs/mm: memblock: add kernel-doc comments for memblock_add[_node] Date: Sat, 30 Jun 2018 17:55:03 +0300 [thread overview] Message-ID: <1530370506-21751-9-git-send-email-rppt@linux.vnet.ibm.com> (raw) In-Reply-To: <1530370506-21751-1-git-send-email-rppt@linux.vnet.ibm.com> Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com> --- mm/memblock.c | 27 +++++++++++++++++++++++++-- 1 file changed, 25 insertions(+), 2 deletions(-) diff --git a/mm/memblock.c b/mm/memblock.c index 8159869..3e6be01 100644 --- a/mm/memblock.c +++ b/mm/memblock.c @@ -595,12 +595,35 @@ int __init_memblock memblock_add_range(struct memblock_type *type, } } +/** + * memblock_add_node - add new memblock region within a NUMA node + * @base: base address of the new region + * @size: size of the new region + * @nid: nid of the new region + * + * Add new memblock region [@base, @base + @size) to the "memory" + * type. See memblock_add_range() description for mode details + * + * Return: + * 0 on success, -errno on failure. + */ int __init_memblock memblock_add_node(phys_addr_t base, phys_addr_t size, int nid) { return memblock_add_range(&memblock.memory, base, size, nid, 0); } +/** + * memblock_add - add new memblock region + * @base: base address of the new region + * @size: size of the new region + * + * Add new memblock region [@base, @base + @size) to the "memory" + * type. See memblock_add_range() description for mode details + * + * Return: + * 0 on success, -errno on failure. + */ int __init_memblock memblock_add(phys_addr_t base, phys_addr_t size) { phys_addr_t end = base + size - 1; @@ -1464,9 +1487,9 @@ void __init __memblock_free_early(phys_addr_t base, phys_addr_t size) memblock_remove_range(&memblock.reserved, base, size); } -/* +/** * __memblock_free_late - free bootmem block pages directly to buddy allocator - * @addr: phys starting address of the boot memory block + * @base: phys starting address of the boot memory block * @size: size of the boot memory block in bytes * * This is only useful when the bootmem allocator has already been torn -- 2.7.4 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-06-30 14:55 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-06-30 14:54 [PATCH v2 00/11] docs/mm: add boot time memory management docs Mike Rapoport 2018-06-30 14:54 ` Mike Rapoport 2018-06-30 14:54 ` [PATCH v2 01/11] mm/bootmem: drop duplicated kernel-doc comments Mike Rapoport 2018-06-30 14:54 ` Mike Rapoport 2018-06-30 14:54 ` [PATCH v2 02/11] docs/mm: nobootmem: fixup " Mike Rapoport 2018-06-30 14:54 ` Mike Rapoport 2018-06-30 14:54 ` [PATCH v2 03/11] docs/mm: bootmem: fix kernel-doc warnings Mike Rapoport 2018-06-30 14:54 ` Mike Rapoport 2018-06-30 14:54 ` [PATCH v2 04/11] docs/mm: bootmem: add kernel-doc description of 'struct bootmem_data' Mike Rapoport 2018-06-30 14:54 ` Mike Rapoport 2018-06-30 14:55 ` [PATCH v2 05/11] docs/mm: bootmem: add overview documentation Mike Rapoport 2018-06-30 14:55 ` Mike Rapoport 2018-06-30 14:55 ` [PATCH v2 06/11] mm/memblock: add a name for memblock flags enumeration Mike Rapoport 2018-06-30 14:55 ` Mike Rapoport 2018-07-12 8:00 ` Michal Hocko 2018-07-12 8:00 ` Michal Hocko 2018-06-30 14:55 ` [PATCH v2 07/11] docs/mm: memblock: update kernel-doc comments Mike Rapoport 2018-06-30 14:55 ` Mike Rapoport 2018-06-30 14:55 ` Mike Rapoport [this message] 2018-06-30 14:55 ` [PATCH v2 08/11] docs/mm: memblock: add kernel-doc comments for memblock_add[_node] Mike Rapoport 2018-06-30 14:55 ` [PATCH v2 09/11] docs/mm: memblock: add kernel-doc description for memblock types Mike Rapoport 2018-06-30 14:55 ` Mike Rapoport 2018-06-30 14:55 ` [PATCH v2 10/11] docs/mm: memblock: add overview documentation Mike Rapoport 2018-06-30 14:55 ` Mike Rapoport 2018-06-30 14:55 ` [PATCH v2 11/11] docs/mm: add description of boot time memory management Mike Rapoport 2018-06-30 14:55 ` Mike Rapoport 2018-07-03 12:23 ` Michal Hocko 2018-07-03 12:23 ` Michal Hocko 2018-07-12 7:26 ` Mike Rapoport 2018-07-12 7:26 ` Mike Rapoport 2018-07-01 15:26 ` [PATCH v2 00/11] docs/mm: add boot time memory management docs Randy Dunlap 2018-07-01 15:26 ` Randy Dunlap 2018-07-02 17:32 ` Jonathan Corbet 2018-07-02 17:32 ` Jonathan Corbet 2018-07-18 11:47 ` Mike Rapoport 2018-07-18 11:47 ` Mike Rapoport 2018-07-18 12:02 ` Jonathan Corbet 2018-07-18 12:02 ` Jonathan Corbet 2018-07-18 17:00 ` Mike Rapoport 2018-07-18 17:00 ` Mike Rapoport 2018-07-26 21:45 ` Jonathan Corbet 2018-07-26 21:45 ` Jonathan Corbet 2018-08-02 18:36 ` Jonathan Corbet 2018-08-02 18:36 ` Jonathan Corbet
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=1530370506-21751-9-git-send-email-rppt@linux.vnet.ibm.com \ --to=rppt@linux.vnet.ibm.com \ --cc=corbet@lwn.net \ --cc=linux-doc@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=rdunlap@infradead.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: linkBe 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.