loongarch.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Huacai Chen <chenhuacai@kernel.org>
To: Max Kellermann <max.kellermann@ionos.com>
Cc: kernel@xen0n.name, lienze@kylinos.cn, yangtiezhu@loongson.cn,
	 tglx@linutronix.de, arnd@arndb.de, loongarch@lists.linux.dev,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH] loongarch/pgtable.h: move {dmw,tlb}_virt_to_page() to page.h
Date: Sun, 10 Mar 2024 22:03:35 +0800	[thread overview]
Message-ID: <CAAhV-H7X2ViBwz7wz3SPmwaxn__9Mo-5pEL9SGe0xON7exj+wA@mail.gmail.com> (raw)
In-Reply-To: <CAKPOu+_j3FTcjpOfS6O+Pr5sFGEC63ofgU8qjHUFbSPRWtS6_Q@mail.gmail.com>

Hi, Max,

On Sun, Mar 10, 2024 at 6:22 PM Max Kellermann <max.kellermann@ionos.com> wrote:
>
> On Sun, Mar 10, 2024 at 2:14 AM Huacai Chen <chenhuacai@kernel.org> wrote:
> > Could you please share what kind of configuration will cause a build error?
>
> With the current kernel, I found none; the problem is masked currently
> due to the current order of include directives, but it caused problems
> during my attempts to clean up linux/mm.h - see
> https://lore.kernel.org/lkml/20240305085919.1601395-1-max.kellermann@ionos.com/
> for the most recent submission; a later (not-yet-submitted) version of
> the series which reproduces the problem can be found here:
> https://github.com/MaxKellermann/linux/commits/mm.h/
OK, I will apply this patch if no one has objections.

Huacai

>
> I saw this problem with "randconfig KCONFIG_SEED=0x5D8A9172" - config attached.
>
> Max

      reply	other threads:[~2024-03-10 14:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08  7:46 [PATCH] loongarch/pgtable.h: move {dmw,tlb}_virt_to_page() to page.h Max Kellermann
2024-03-10  1:14 ` Huacai Chen
2024-03-10 10:22   ` Max Kellermann
2024-03-10 14:03     ` Huacai Chen [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=CAAhV-H7X2ViBwz7wz3SPmwaxn__9Mo-5pEL9SGe0xON7exj+wA@mail.gmail.com \
    --to=chenhuacai@kernel.org \
    --cc=arnd@arndb.de \
    --cc=kernel@xen0n.name \
    --cc=lienze@kylinos.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=max.kellermann@ionos.com \
    --cc=tglx@linutronix.de \
    --cc=yangtiezhu@loongson.cn \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).