From: Mike Rapoport <rppt@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Nick Hu <nickhu@andestech.com>, Greentime Hu <green.hu@gmail.com>,
Vincent Chen <deanbo422@gmail.com>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
Mike Rapoport <rppt@linux.ibm.com>,
Mike Rapoport <rppt@kernel.org>
Subject: Re: [PATCH 0/2] fix recent nds32 build breakage
Date: Fri, 27 Dec 2019 13:07:37 +0200 [thread overview]
Message-ID: <20191227110736.GA30363@rapoport-lnx> (raw)
In-Reply-To: <20191223110004.2157-1-rppt@kernel.org>
Arnd,
Can you please take these via asm-generic tree?
On Mon, Dec 23, 2019 at 01:00:02PM +0200, Mike Rapoport wrote:
> From: Mike Rapoport <rppt@linux.ibm.com>
>
> Hi,
>
> The kbuild robot reported build breakage of nds32 architecture [1] that
> happens with CONFIG_CPU_CACHE_ALIASING=n and CONFIG_HUGHMEM=y.
>
> There are two issues: one with a missing macro during conversion of page
> folding and another one is a conflict between cacheflush.h definitions in
> arch/nds32 and asm-generic.
>
> [1] https://lore.kernel.org/lkml/201912212139.yptX8CsV%25lkp@intel.com/
>
> Mike Rapoport (2):
> asm-generic/nds32: don't redefine cacheflush primitives
> nds32: fix build failure caused by page table folding updates
>
> arch/nds32/include/asm/cacheflush.h | 11 ++++++----
> arch/nds32/include/asm/pgtable.h | 2 +-
> include/asm-generic/cacheflush.h | 33 ++++++++++++++++++++++++++++-
> 3 files changed, 40 insertions(+), 6 deletions(-)
>
> --
> 2.24.0
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2019-12-27 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 11:00 [PATCH 0/2] fix recent nds32 build breakage Mike Rapoport
2019-12-23 11:00 ` [PATCH 1/2] asm-generic/nds32: don't redefine cacheflush primitives Mike Rapoport
2019-12-24 2:13 ` Greentime Hu
2019-12-23 11:00 ` [PATCH 2/2] nds32: fix build failure caused by page table folding updates Mike Rapoport
2019-12-24 2:14 ` Greentime Hu
2019-12-27 11:07 ` Mike Rapoport [this message]
2019-12-30 10:21 ` [PATCH 0/2] fix recent nds32 build breakage 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=20191227110736.GA30363@rapoport-lnx \
--to=rppt@kernel.org \
--cc=arnd@arndb.de \
--cc=deanbo422@gmail.com \
--cc=green.hu@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickhu@andestech.com \
--cc=rppt@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).