archive mirror
 help / color / mirror / Atom feed
From: Sumit Semwal <>
To: Stephen Rothwell <>
Cc: Linux-Next Mailing List <>,
	Linux Kernel Mailing List <>
Subject: Re: linux-next: Tree for Jun 9
Date: Fri, 9 Jun 2017 19:28:13 +0530	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Stephen,

On 9 June 2017 at 12:12, Stephen Rothwell <> wrote:
> Hi all,
< snip >
> You can see which trees have been included by looking in the Next/Trees
> file in the source.  There are also quilt-import.log and merge.log
> files in the Next directory.  Between each merge, the tree was built
> with a ppc64_defconfig for powerpc and an allmodconfig (with
> CONFIG_BUILD_DOCSRC=n) for x86_64, a multi_v7_defconfig for arm and a
> native build of tools/perf. After the final fixups (if any), I do an
> x86_64 modules_install followed by builds for x86_64 allnoconfig,
> powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig
> and pseries_le_defconfig and i386, sparc and sparc64 defconfig. And
> finally, a simple boot test of the powerpc pseries_le_defconfig kernel
> in qemu.
Thanks very much for this! I was trying to build this with the arm64
defconfig, and it doesn't build due to multiple instance of "emac:
ethernet@1c30000" in arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi.
With one instance removed, the build completes successfully.

It seems to be a merge issue, since the duplicate instance is added by
commit 9afca2c4e379f - just thought I'd let you know.


Best regards,

  reply	other threads:[~2017-06-09 13:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-09  6:42 linux-next: Tree for Jun 9 Stephen Rothwell
2017-06-09 13:58 ` Sumit Semwal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-09  4:13 Stephen Rothwell
2021-06-09 12:57 Stephen Rothwell
2020-06-09 12:59 Stephen Rothwell
2016-06-09  6:34 Stephen Rothwell
2016-06-09 22:06 ` Sudip Mukherjee
2016-06-09 22:14   ` Kees Cook
2016-06-11  1:05     ` Paul Gortmaker
2015-06-09 14:44 Stephen Rothwell

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \

* 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).