From: wlfightup@gmail.com
To: mike.kravetz@oracle.com, muchun.song@linux.dev,
akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
wlfightup <wlfightup@gmail.com>
Subject: [PATCH] hugetlbfs: Fixed code style, adding a blank line between functions
Date: Mon, 2 Jan 2023 21:54:53 +0800 [thread overview]
Message-ID: <20230102135453.31609-1-wlfightup@gmail.com> (raw)
From: wlfightup <wlfightup@gmail.com>
The code style must uniform, and the functions cannot be
separated without blank line
Signed-off-by: wlfightup <wlfightup@gmail.com>
---
mm/hugetlb.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index db895230ee7e..4ad2be7f3b83 100644
--- a/mm/hugetlb.c
+++ b/mm/hugetlb.c
@@ -3213,6 +3213,7 @@ static void __init gather_bootmem_prealloc(void)
cond_resched();
}
}
+
static void __init hugetlb_hstate_alloc_pages_onenode(struct hstate *h, int nid)
{
unsigned long i;
--
2.24.3 (Apple Git-128)
reply other threads:[~2023-01-02 13:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230102135453.31609-1-wlfightup@gmail.com \
--to=wlfightup@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=muchun.song@linux.dev \
/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