From: Thomas Gleixner <tglx@linutronix.de>
To: Arnd Bergmann <arnd@arndb.de>, kernel test robot <lkp@intel.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
x86@kernel.org, Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [tip:timers/vdso 11/13] include/vdso/page.h:15:39: error: 'CONFIG_PAGE_SHIFT' undeclared here (not in a function); did you mean 'CONFIG_LOG_BUF_SHIFT'?
Date: Wed, 30 Oct 2024 00:45:24 +0100 [thread overview]
Message-ID: <87iktazd63.ffs@tglx> (raw)
In-Reply-To: <1d6a10ca-3d86-452a-bdba-03a1204dd232@app.fastmail.com>
On Tue, Oct 29 2024 at 22:05, Arnd Bergmann wrote:
> On Tue, Oct 29, 2024, at 21:18, Thomas Gleixner wrote:
>
> Part of the problem here is that this simpler patch
> then just causes different build failures for the
> same configurations, since m68k kernels cannot successfully
> build when no platform is selected.
But that's a problem which existed before all of that PAGE* changes,
right?
Geert, can you please take care of that magic Kconfig maze in m68k as
I'm completely lost how that is supposed to work?
Thanks,
tglx
next prev parent reply other threads:[~2024-10-29 23:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 22:38 [tip:timers/vdso 11/13] include/vdso/page.h:15:39: error: 'CONFIG_PAGE_SHIFT' undeclared here (not in a function); did you mean 'CONFIG_LOG_BUF_SHIFT'? kernel test robot
2024-10-29 21:18 ` Thomas Gleixner
2024-10-29 22:05 ` Arnd Bergmann
2024-10-29 23:45 ` Thomas Gleixner [this message]
2024-10-30 8:49 ` Geert Uytterhoeven
2024-10-30 9:05 ` Arnd Bergmann
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=87iktazd63.ffs@tglx \
--to=tglx@linutronix.de \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vincenzo.frascino@arm.com \
--cc=x86@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 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.