From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Christoph Hellwig <hch@lst•de>
Cc: Alexey Kardashevskiy <aik@ozlabs•ru>,
Michael Ellerman <mpe@ellerman•id.au>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the dma-mapping tree
Date: Fri, 27 Nov 2020 20:59:03 +1100 [thread overview]
Message-ID: <20201127205903.0e294acf@canb.auug.org.au> (raw)
In-Reply-To: <20201127092137.GA14170@lst.de>
[-- Attachment #1: Type: text/plain, Size: 595 bytes --]
Hi Christoph,
On Fri, 27 Nov 2020 10:21:37 +0100 Christoph Hellwig <hch@lst•de> wrote:
>
> On Fri, Nov 27, 2020 at 05:58:01PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the dma-mapping tree, today's linux-next build (powerpc64
> > allnoconfig) failed like this:
>
> I'm looking into fixing this now, but how do you generate a powerpc64
> allnoconfig? My attempts so far either create a ppc32 one or fail entirely.
echo CONFIG_PPC64=y >tmp_conf
KCONFIG_ALLCONFIG=tmp_conf make ARCH=powerpc allnoconfig
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-11-27 9:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 6:58 linux-next: build failure after merge of the dma-mapping tree Stephen Rothwell
2020-11-27 9:21 ` Christoph Hellwig
2020-11-27 9:59 ` Stephen Rothwell [this message]
2020-11-27 9:33 ` Christoph Hellwig
[not found] <CGME20260327200715eucas1p1953ce4c0b4d4e0cd95844f0acdb7ac3a@eucas1p1.samsung.com>
2026-03-27 20:07 ` Mark Brown
2026-03-30 7:56 ` Marek Szyprowski
2026-03-30 8:11 ` Maxime Ripard
-- strict thread matches above, loose matches on Subject: below --
2024-07-10 1:05 Stephen Rothwell
2024-07-10 5:58 ` Christoph Hellwig
2024-05-07 23:16 Stephen Rothwell
2024-05-08 6:51 ` Christoph Hellwig
2024-05-08 8:51 ` Alexander Lobakin
2024-05-08 13:45 ` Christoph Hellwig
2012-02-13 5:40 Stephen Rothwell
2012-02-13 7:31 ` Kyungmin Park
2012-02-13 15:05 ` Marek Szyprowski
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=20201127205903.0e294acf@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=aik@ozlabs$(echo .)ru \
--cc=hch@lst$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mpe@ellerman$(echo .)id.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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