From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, peterx@redhat.com,
akpm@linux-foundation.org, akpm@linux-foundation.org
Subject: + mm-hugetlb-introduce-hugetlb_walk-checkpatch-fixes.patch added to mm-unstable branch
Date: Fri, 16 Dec 2022 09:20:14 -0800 [thread overview]
Message-ID: <20221216172015.45242C433D2@smtp.kernel.org> (raw)
The patch titled
Subject: mm-hugetlb-introduce-hugetlb_walk-checkpatch-fixes
has been added to the -mm mm-unstable branch. Its filename is
mm-hugetlb-introduce-hugetlb_walk-checkpatch-fixes.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-hugetlb-introduce-hugetlb_walk-checkpatch-fixes.patch
This patch will later appear in the mm-unstable branch at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next via the mm-everything
branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there every 2-3 working days
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: mm-hugetlb-introduce-hugetlb_walk-checkpatch-fixes
Date: Fri Dec 16 09:19:24 AM PST 2022
ERROR: code indent should use tabs where possible
#267: FILE: mm/page_vma_mapped.c:172:
+ * All callers that get here will already hold the$
ERROR: code indent should use tabs where possible
#268: FILE: mm/page_vma_mapped.c:173:
+ * i_mmap_rwsem. Therefore, no additional locks need to be$
ERROR: code indent should use tabs where possible
#269: FILE: mm/page_vma_mapped.c:174:
+ * taken before calling hugetlb_walk().$
total: 3 errors, 0 warnings, 211 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
NOTE: Whitespace errors detected.
You may wish to use scripts/cleanpatch or scripts/cleanfile
./patches/mm-hugetlb-introduce-hugetlb_walk.patch has style problems, please review.
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
Please run checkpatch prior to sending patches
Cc: Peter Xu <peterx@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/page_vma_mapped.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--- a/mm/page_vma_mapped.c~mm-hugetlb-introduce-hugetlb_walk-checkpatch-fixes
+++ a/mm/page_vma_mapped.c
@@ -169,9 +169,9 @@ bool page_vma_mapped_walk(struct page_vm
if (pvmw->pte)
return not_found(pvmw);
/*
- * All callers that get here will already hold the
- * i_mmap_rwsem. Therefore, no additional locks need to be
- * taken before calling hugetlb_walk().
+ * All callers that get here will already hold the
+ * i_mmap_rwsem. Therefore, no additional locks need to be
+ * taken before calling hugetlb_walk().
*/
pvmw->pte = hugetlb_walk(vma, pvmw->address, size);
if (!pvmw->pte)
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
mm-memfd-add-mfd_noexec_seal-and-mfd_exec-fix.patch
mm-hugetlb-introduce-hugetlb_walk-checkpatch-fixes.patch
error-injection-remove-ei_etype_none-fix.patch
reply other threads:[~2022-12-16 17:20 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=20221216172015.45242C433D2@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=peterx@redhat.com \
/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.