From: wale zhang <wale.zhang.ftd@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Barry Song <21cnbao@gmail.com>,
akpm@linux-foundation.org, lorenzo.stoakes@oracle.com,
chrisl@kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 1/1] mm,swapops: Fix compile error on set_pmd_migration_entry.
Date: Tue, 30 Dec 2025 16:05:04 +0800 [thread overview]
Message-ID: <CAHrEdes6Usi0Amc0mf_1ZZ4MLbTxWYor9bjNOm9v7GNx8DMMxA@mail.gmail.com> (raw)
In-Reply-To: <aVNccyCxjCPRjJiS@casper.infradead.org>
On Tue, Dec 30, 2025 at 1:00 PM Matthew Wilcox <willy@infradead.org> wrote:
>
> On Fri, Dec 26, 2025 at 07:45:48PM +0800, wale zhang wrote:
> > I compile the 6.19-rc2 for arm64 with -O0, this kind of error log will appear.
>
> I don't think we support compilation with -O0. Why did you think this
> would work, and why did you think this was a good idea?
Hello Matthew,
Compilation with -O0 is mainly for beginners to learn and debug.
I don't want to encounter the same problems every time I pull the
latest code. Perhaps other people will also encounter the same
problem.
And I see that include/linux/pgtable.h has the same usage.
320 static inline int pmdp_set_access_flags(struct vm_area_struct *vma,
321 unsigned long address, pmd_t *pmdp,
322 pmd_t entry, int dirty)
323 {
324 BUILD_BUG();
325 return 0;
326 }
Thanks
Wale
prev parent reply other threads:[~2025-12-30 8:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 9:40 Wale Zhang
2025-12-25 10:22 ` Barry Song
2025-12-26 11:45 ` wale zhang
2025-12-26 18:43 ` Barry Song
2025-12-27 7:51 ` wale zhang
2025-12-27 8:16 ` Barry Song
2025-12-27 9:58 ` wale zhang
2025-12-27 11:25 ` Barry Song
2025-12-28 21:37 ` Andrew Morton
2025-12-28 22:07 ` Barry Song
2025-12-29 11:37 ` wale zhang
2025-12-30 5:00 ` Matthew Wilcox
2025-12-30 8:05 ` wale zhang [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=CAHrEdes6Usi0Amc0mf_1ZZ4MLbTxWYor9bjNOm9v7GNx8DMMxA@mail.gmail.com \
--to=wale.zhang.ftd@gmail.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chrisl@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=willy@infradead.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