linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Randy Dunlap <rdunlap@infradead.org>,
	akpm@linux-foundation.org, broonie@kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
	mm-commits@vger.kernel.org, sfr@canb.auug.org.au
Subject: Re: mmotm 2021-05-12-21-46 uploaded (arch/x86/mm/pgtable.c)
Date: Thu, 13 May 2021 19:09:23 +0200	[thread overview]
Message-ID: <54055e72-34b8-d43d-2ad3-87e8c8fa547b@csgroup.eu> (raw)
In-Reply-To: <151ddd7f-1d3e-a6f7-daab-e32f785426e1@infradead.org>



Le 13/05/2021 à 17:54, Randy Dunlap a écrit :
> On 5/12/21 9:47 PM, akpm@linux-foundation.org wrote:
>> The mm-of-the-moment snapshot 2021-05-12-21-46 has been uploaded to
>>
>>     https://www.ozlabs.org/~akpm/mmotm/
>>
>> mmotm-readme.txt says
>>
>> README for mm-of-the-moment:
>>
>> https://www.ozlabs.org/~akpm/mmotm/
>>
>> This is a snapshot of my -mm patch queue.  Uploaded at random hopefully
>> more than once a week.
>>
>> You will need quilt to apply these patches to the latest Linus release (5.x
>> or 5.x-rcY).  The series file is in broken-out.tar.gz and is duplicated in
>> https://ozlabs.org/~akpm/mmotm/series
> 
> 
> on i386:
> 
> ../arch/x86/mm/pgtable.c:703:5: error: redefinition of ‘pud_set_huge’
>   int pud_set_huge(pud_t *pud, phys_addr_t addr, pgprot_t prot)
>       ^~~~~~~~~~~~
> In file included from ../include/linux/mm.h:33:0,
>                   from ../arch/x86/mm/pgtable.c:2:
> ../include/linux/pgtable.h:1387:19: note: previous definition of ‘pud_set_huge’ was here
>   static inline int pud_set_huge(pud_t *pud, phys_addr_t addr, pgprot_t prot)
>                     ^~~~~~~~~~~~
> ../arch/x86/mm/pgtable.c:758:5: error: redefinition of ‘pud_clear_huge’
>   int pud_clear_huge(pud_t *pud)
>       ^~~~~~~~~~~~~~
> In file included from ../include/linux/mm.h:33:0,
>                   from ../arch/x86/mm/pgtable.c:2:
> ../include/linux/pgtable.h:1391:19: note: previous definition of ‘pud_clear_huge’ was here
>   static inline int pud_clear_huge(pud_t *pud)
>                     ^~~~~~~~~~~~~~

Hum ...

Comes from my patch 
https://patchwork.ozlabs.org/project/linuxppc-dev/patch/5ac5976419350e8e048d463a64cae449eb3ba4b0.1620795204.git.christophe.leroy@csgroup.eu/

But, that happens only if x86 defines __PAGETABLE_PUD_FOLDED. And if PUD is folded, then I can't 
understand my it has pud_set_huge() and pud_clear_huge() functions.

Christophe


  reply	other threads:[~2021-05-13 17:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-13  4:47 mmotm 2021-05-12-21-46 uploaded akpm
2021-05-13  5:28 ` mmotm 2021-05-12-21-46 uploaded (mm/memory_failure.c) Randy Dunlap
2021-05-13  5:36   ` HORIGUCHI NAOYA(堀口 直也)
2021-05-13 15:54 ` mmotm 2021-05-12-21-46 uploaded (arch/x86/mm/pgtable.c) Randy Dunlap
2021-05-13 17:09   ` Christophe Leroy [this message]
2021-05-13 20:47     ` Andrew Morton
2021-05-13 21:08       ` Randy Dunlap
2021-05-14  9:45         ` Naresh Kamboju
2021-05-14 21:40           ` 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=54055e72-34b8-d43d-2ad3-87e8c8fa547b@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=mm-commits@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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