From: Rebecca Mckeever <remckee0@gmail.com>
To: outreachy@lists.linux.dev
Cc: Mike Rapoport <rppt@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
David Hildenbrand <david@redhat.com>,
Rebecca Mckeever <remckee0@gmail.com>
Subject: [PATCH v2 0/4] memblock tests: update style of comments
Date: Fri, 22 Apr 2022 07:55:34 -0500 [thread overview]
Message-ID: <cover.1650631746.git.remckee0@gmail.com> (raw)
These patches update the style of comments for memblock_add_*(),
memblock_reserve_*(), memblock_remove_*(), and memblock_free_*()
functions to match the style of comments in tests/alloc_*.c and
remove extra spaces in those comments to conform to Linux kernel
coding style.
Rebecca Mckeever (4):
memblock tests: update style of comments for memblock_add_*()
functions
memblock tests: update style of comments for memblock_reserve_*()
functions
memblock tests: update style of comments for memblock_remove_*()
functions
memblock tests: update style of comments for memblock_free_*()
functions
tools/testing/memblock/tests/basic_api.c | 350 +++++++++++++++++------
1 file changed, 256 insertions(+), 94 deletions(-)
--
2.32.0
next reply other threads:[~2022-04-22 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 12:55 Rebecca Mckeever [this message]
2022-04-22 12:55 ` [PATCH v2 1/4] memblock tests: update style of comments for memblock_add_*() functions Rebecca Mckeever
2022-04-22 12:55 ` [PATCH v2 2/4] memblock tests: update style of comments for memblock_reserve_*() functions Rebecca Mckeever
2022-04-22 12:55 ` [PATCH v2 3/4] memblock tests: update style of comments for memblock_remove_*() functions Rebecca Mckeever
2022-04-22 12:55 ` [PATCH v2 4/4] memblock tests: update style of comments for memblock_free_*() functions Rebecca Mckeever
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=cover.1650631746.git.remckee0@gmail.com \
--to=remckee0@gmail.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=outreachy@lists.linux.dev \
--cc=rppt@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 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.