From: Gavin Shan <gshan@redhat.com>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, alexander.duyck@gmail.com,
david@redhat.com, mst@redhat.com, akpm@linux-foundation.org,
anshuman.khandual@arm.com, catalin.marinas@arm.com,
will@kernel.org, shan.gavin@gmail.com
Subject: [PATCH v2 1/3] mm/page_reporting: Fix code style in __page_reporting_request()
Date: Tue, 22 Jun 2021 15:49:24 +0800 [thread overview]
Message-ID: <20210622074926.333223-2-gshan@redhat.com> (raw)
In-Reply-To: <20210622074926.333223-1-gshan@redhat.com>
The lines of comments would be starting with one, instead two space.
This corrects the style.
Signed-off-by: Gavin Shan <gshan@redhat.com>
---
mm/page_reporting.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/mm/page_reporting.c b/mm/page_reporting.c
index c50d93ffa252..df9c5054e1b4 100644
--- a/mm/page_reporting.c
+++ b/mm/page_reporting.c
@@ -31,8 +31,8 @@ __page_reporting_request(struct page_reporting_dev_info *prdev)
return;
/*
- * If reporting is already active there is nothing we need to do.
- * Test against 0 as that represents PAGE_REPORTING_IDLE.
+ * If reporting is already active there is nothing we need to do.
+ * Test against 0 as that represents PAGE_REPORTING_IDLE.
*/
state = atomic_xchg(&prdev->state, PAGE_REPORTING_REQUESTED);
if (state != PAGE_REPORTING_IDLE)
--
2.23.0
next prev parent reply other threads:[~2021-06-22 5:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 7:49 [PATCH v2 0/3] mm/page_reporting: Make page reporting work on arm64 with 64KB page size Gavin Shan
2021-06-22 7:49 ` Gavin Shan [this message]
2021-06-22 7:49 ` [PATCH v2 2/3] mm/page_reporting: Allow driver to specify threshold Gavin Shan
2021-06-22 17:39 ` Alexander Duyck
2021-06-23 0:43 ` Gavin Shan
2021-06-22 7:49 ` [PATCH v2 3/3] virtio_balloon: Specify page reporting order if needed Gavin Shan
2021-06-22 17:44 ` Alexander Duyck
2021-06-23 0:47 ` Gavin Shan
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=20210622074926.333223-2-gshan@redhat.com \
--to=gshan@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.duyck@gmail.com \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mst@redhat.com \
--cc=shan.gavin@gmail.com \
--cc=will@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