From: "Arnd Bergmann" <arnd@arndb.de>
To: "Geert Uytterhoeven" <geert@linux-m68k.org>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
"kernel test robot" <lkp@intel.com>,
"Vincenzo Frascino" <vincenzo.frascino@arm.com>,
oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
x86@kernel.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 09:05:15 +0000 [thread overview]
Message-ID: <b2b3d30d-12ad-4022-a12b-e2d011952f0f@app.fastmail.com> (raw)
In-Reply-To: <CAMuHMdUAdV5Qv1AXKqLGi4xoM=9uiygSDKqhLnZ5YxzXsN6SxA@mail.gmail.com>
On Wed, Oct 30, 2024, at 08:49, Geert Uytterhoeven wrote:
> On Tue, Oct 29, 2024 at 11:05 PM Arnd Bergmann <arnd@arndb.de> wrote:
>> On Tue, Oct 29, 2024, at 21:18, Thomas Gleixner wrote:
>> I have previously suggested a similar but more extensive patch
>> to address the problem:
>>
>> https://lore.kernel.org/all/CAMuHMdVC-FUSA5C9aNrvP3=RaRWrchhUEC5UYcSGMz_ep1PEhg@mail.gmail.com/
>>
>> I can rebase that one if Geert still wants it. I think I sent
>
> I am still interested ;-)
>
>> an updated version somewhere but can't find it now.
>
> AFAIK you haven't, so there are still outstanding review comments on
> the last version you sent...
> Thanks!
Ok, sorry it slipped through, I'll send an updated version
later today then.
Arnd
prev parent reply other threads:[~2024-10-30 9:05 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
2024-10-30 8:49 ` Geert Uytterhoeven
2024-10-30 9:05 ` Arnd Bergmann [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=b2b3d30d-12ad-4022-a12b-e2d011952f0f@app.fastmail.com \
--to=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=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox