From: Thomas Gleixner <tglx@linutronix.de>
To: Jann Horn <jannh@google.com>
Cc: Andrei Vagin <avagin@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] time/namespace: Refactor copy-pasted helper into one copy
Date: Wed, 30 Nov 2022 11:57:14 +0100 [thread overview]
Message-ID: <87k03cu2ut.ffs@tglx> (raw)
In-Reply-To: <CAG48ez1_uq6a4rq_89Ua=2P1jSsDV7u4fCh2y13X9v2JfC5MsA@mail.gmail.com>
On Wed, Nov 30 2022 at 11:15, Jann Horn wrote:
> On Tue, Nov 29, 2022 at 8:18 PM Jann Horn <jannh@google.com> wrote:
>> find_timens_vvar_page() is not arch-specific, as can be seen from how all
>> five per-architecture versions of it are the same.
>> (arm64, powerpc and riscv are exactly the same; x86 and s390 have two
>> characters difference inside a comment, less blank lines, and mark the
>> !CONFIG_TIME_NS version as inline.)
>>
>> Refactor the five copies into a central copy in kernel/time/namespace.c.
>>
>> Marked for stable backporting because it is a prerequisite for the
>> following patch.
>>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Jann Horn <jannh@google.com>
>
> Should I resend this one without the Cc stable as a standalone cleanup patch?
Yes, please.
prev parent reply other threads:[~2022-11-30 10:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 19:18 [PATCH 1/2] time/namespace: Refactor copy-pasted helper into one copy Jann Horn
2022-11-29 19:18 ` [PATCH 2/2] time/namespace: Forbid timens page faults under kthread_use_mm() Jann Horn
2022-11-29 21:18 ` Thomas Gleixner
2022-11-29 22:28 ` Jann Horn
2022-11-29 22:34 ` Jann Horn
2022-11-30 0:09 ` Thomas Gleixner
2022-11-30 0:07 ` Thomas Gleixner
2022-11-30 22:48 ` David Laight
2022-12-01 9:31 ` Jann Horn
2022-11-30 10:15 ` [PATCH 1/2] time/namespace: Refactor copy-pasted helper into one copy Jann Horn
2022-11-30 10:57 ` Thomas Gleixner [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=87k03cu2ut.ffs@tglx \
--to=tglx@linutronix.de \
--cc=avagin@gmail.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.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.