All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com,
	luto@kernel.org, hpa@zytor.com, dave.hansen@linux.intel.com,
	bp@alien8.de, kunyu@nfschina.com
Subject: Re: + mm-functions-may-simplify-the-use-of-return-values.patch added to mm-unstable branch
Date: Mon, 9 May 2022 09:20:35 +0200	[thread overview]
Message-ID: <20220509072035.GG76023@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20220507175027.38900C385A6@smtp.kernel.org>

On Sat, May 07, 2022 at 10:50:26AM -0700, Andrew Morton wrote:
> 
> The patch titled
>      Subject: mm: functions may simplify the use of return values
> has been added to the -mm mm-unstable branch.  Its filename is
>      mm-functions-may-simplify-the-use-of-return-values.patch
> 
> This patch should soon 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: Li kunyu <kunyu@nfschina.com>
> Subject: mm: functions may simplify the use of return values
> 
> p4d_clear_huge may be optimized for void return type and function usage. 
> vunmap_p4d_range function saves a few steps here.
> 
> Link: https://lkml.kernel.org/r/20220507150630.90399-1-kunyu@nfschina.com
> Signed-off-by: Li kunyu <kunyu@nfschina.com>
> Cc: Dave Hansen <dave.hansen@linux.intel.com>
> Cc: Andy Lutomirski <luto@kernel.org>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Borislav Petkov <bp@alien8.de>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

Please, no:

arch/x86/mm/pgtable.c: * p4d_clear_huge - clear kernel P4D mapping when it is set
arch/x86/mm/pgtable.c:int p4d_clear_huge(p4d_t *p4d)
arch/x86/mm/pgtable.c: * pud_clear_huge - clear kernel PUD mapping when it is set
arch/x86/mm/pgtable.c:int pud_clear_huge(pud_t *pud)
arch/x86/mm/pgtable.c: * pmd_clear_huge - clear kernel PMD mapping when it is set
arch/x86/mm/pgtable.c:int pmd_clear_huge(pmd_t *pmd)

why would the p4d one need to be different from the rest?

  reply	other threads:[~2022-05-09  7:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-07 17:50 + mm-functions-may-simplify-the-use-of-return-values.patch added to mm-unstable branch Andrew Morton
2022-05-09  7:20 ` Peter Zijlstra [this message]
2022-05-09 17:07   ` Andrew Morton

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=20220509072035.GG76023@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kunyu@nfschina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=mm-commits@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.