From: Mike Rapoport <rppt@kernel.org>
To: Christian Dietrich <christian.dietrich@tuhh.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@linux.ibm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] mm/pgtable: define pte_index so that preprocessor could recognize it
Date: Tue, 11 Jan 2022 19:10:52 +0200 [thread overview]
Message-ID: <Yd26HEL4PvKdSaTQ@kernel.org> (raw)
In-Reply-To: <s7bzgo2cn99.fsf@dokucode.de>
Hi Christian,
On Tue, Jan 11, 2022 at 04:20:34PM +0100, Christian Dietrich wrote:
> Hello Mike!
>
> Mike Rapoport <rppt@kernel.org> [11. Januar 2022]:
>
> > diff --git a/include/linux/pgtable.h b/include/linux/pgtable.h
> > index e24d2c992b11..d468efcf48f4 100644
> > --- a/include/linux/pgtable.h
> > +++ b/include/linux/pgtable.h
> > @@ -62,6 +62,7 @@ static inline unsigned long pte_index(unsigned long address)
> > {
> > return (address >> PAGE_SHIFT) & (PTRS_PER_PTE - 1);
> > }
> > +#define pte_index pte_index
>
> Wouldn't it make sense to remove the dead CPP blocks (#ifdef pte_index)
> from mm/memory.c?
It does make sense to remove the dead code, but this cleanup does not need
stable backporting so it'll be a separate patch.
Care to send a patch? ;-)
> Or is there a case were pte_index is not defined for an architecture?
Nope, the fix in include/linux/pgtable.h covers MMU architectures and NOMMU
do not compile mm/memory.c anyway.
> chris
> --
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2022-01-11 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 14:54 Mike Rapoport
2022-01-11 15:20 ` Christian Dietrich
2022-01-11 17:10 ` Mike Rapoport [this message]
2022-01-11 18:44 ` Khalid Aziz
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=Yd26HEL4PvKdSaTQ@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=christian.dietrich@tuhh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.ibm.com \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox