From: Peter Zijlstra <peterz@infradead.org>
To: Zach O'Keefe <zokeefe@google.com>
Cc: kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: [peterz-queue:x86/mm.pae 5/9] mm/khugepaged.c:865:16: error: implicit declaration of function 'pmd_read_atomic'
Date: Fri, 14 Oct 2022 11:16:32 +0200 [thread overview]
Message-ID: <Y0ko8GLvpO31qTCr@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAAa6QmTMa76hsaN_RDkkQRpEcH8VV-RqHY=MXWjk36eMX49Ppg@mail.gmail.com>
On Thu, Oct 13, 2022 at 10:15:13AM -0700, Zach O'Keefe wrote:
> Seems like this was just due to local "mm: Rename pmd_read_atomic()"
> conflict after merging Linus's tree (which introduced another
> pmd_read_atomic() callsite). Peter already seems to have rebased and
> made the fix - thanks Peter.
Yep, just needed a fixup. Patch applied but didn't build. Arguably I
should've compiled before pushing, but meh :-)
prev parent reply other threads:[~2022-10-14 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 13:49 [peterz-queue:x86/mm.pae 5/9] mm/khugepaged.c:865:16: error: implicit declaration of function 'pmd_read_atomic' kernel test robot
2022-10-13 17:15 ` Zach O'Keefe
2022-10-14 9:16 ` Peter Zijlstra [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=Y0ko8GLvpO31qTCr@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=zokeefe@google.com \
/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