From: Andrew Morton <akpm@linux-foundation.org>
To: Jeongjun Park <aha310510@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
usama.anjum@collabora.com, peterx@redhat.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] mm: remove the newlines, which are added for unknown reasons and interfere with bug analysis
Date: Mon, 7 Oct 2024 18:25:46 -0700 [thread overview]
Message-ID: <20241007182546.7f3ac958c7a3bc408420549a@linux-foundation.org> (raw)
In-Reply-To: <CAO9qdTGSaJZ0oTmWqRouU45ur3drQVxRaH8aaBB99DXAoA40_A@mail.gmail.com>
On Mon, 7 Oct 2024 20:24:57 +0900 Jeongjun Park <aha310510@gmail.com> wrote:
> > > Since I cannot modify the source code printing function of the git.kernel.org
> > > site, the best solution I can suggest is to remove the unnecessary line break
> > > character that exists in all versions.
> >
> > I would recommend fixing the git.kernel.org code, it is all open source
> > and can be fixed up, as odds are other projects/repos would like to have
> > it fixed as well.
> >
>
> Oh, I just realized that this website is open source and written in C.
>
> This seems to be the correct git repository, so I'll commit here.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/zx2c4/cgit.git
Still, we don't want that newline in there. I did this as a little
cleanup. Please send a new (similar) patch if you're prefer.
From: Andrew Morton <akpm@linux-foundation.org>
Subject: mm/memory.c: remove stray newline at top of file
Date: Mon Oct 7 06:20:09 PM PDT 2024
Fixes: d61ea1cb0095 ("userfaultfd: UFFD_FEATURE_WP_ASYNC")
Reported-by: Jeongjun Park <aha310510@gmail.com>
Closes: https://lkml.kernel.org/r/20241007065307.4158-1-aha310510@gmail.com
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>
Cc: Peter Xu <peterx@redhat.com>
Cc: Greg KH <gregkh@linuxfoundation.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/memory.c | 1 -
1 file changed, 1 deletion(-)
--- a/mm/memory.c~mm-memoryc-remove-stray-newline-at-top-of-file
+++ a/mm/memory.c
@@ -1,4 +1,3 @@
-
// SPDX-License-Identifier: GPL-2.0-only
/*
* linux/mm/memory.c
_
prev parent reply other threads:[~2024-10-08 1:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 6:53 [PATCH] mm: remove the newlines, which are added for unknown reasons and interfere with bug analysis Jeongjun Park
2024-10-07 8:24 ` Greg KH
2024-10-07 8:57 ` Jeongjun Park
2024-10-07 9:05 ` Greg KH
2024-10-07 11:24 ` Jeongjun Park
2024-10-07 11:31 ` Muhammad Usama Anjum
2024-10-08 1:25 ` Andrew Morton [this message]
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=20241007182546.7f3ac958c7a3bc408420549a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aha310510@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=stable@vger.kernel.org \
--cc=usama.anjum@collabora.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.