Re: linux-next: manual merge of the kbuild tree with Linus' tree

From	Michal Marek <mmarek@suse.cz>
Newsgroups	linux.kernel
Subject	Re: linux-next: manual merge of the kbuild tree with Linus' tree
Date	2016-09-12 11:10 +0200
Message-ID	<sgvpv-1eW-5@gated-at.bofh.it> (permalink)
References	<sgoo2-5bR-5@gated-at.bofh.it> <sgpDr-5X1-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 2016-09-12 04:53, Nicholas Piggin wrote:
> Question, what is the best way to merge dependent patches? Considering
> they will need a good amount of architecture testing, I think they will
> have to go via arch trees. But it also does not make sense to merge these
> kbuild changes upstream first, without having tested them.

I think it makes sense to merge the kbuild changes via kbuild.git, even
if they are unused and untested. Any follow-up fixes required to enable
the first architecture can go through the respective architecture tree.
Does that sound OK?

Michal

Thread

linux-next: manual merge of the kbuild tree with Linus' tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-09-12 03:40 +0200
  Re: linux-next: manual merge of the kbuild tree with Linus' tree Nicholas Piggin <npiggin@gmail.com> - 2016-09-12 05:00 +0200
    Re: linux-next: manual merge of the kbuild tree with Linus' tree Michal Marek <mmarek@suse.cz> - 2016-09-12 11:10 +0200
      Re: linux-next: manual merge of the kbuild tree with Linus' tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-09-13 01:50 +0200
        Re: linux-next: manual merge of the kbuild tree with Linus' tree Nicholas Piggin <npiggin@gmail.com> - 2016-09-13 06:10 +0200
        Re: linux-next: manual merge of the kbuild tree with Linus' tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-09-13 06:10 +0200
          Re: linux-next: manual merge of the kbuild tree with Linus' tree Nicholas Piggin <npiggin@gmail.com> - 2016-09-13 11:20 +0200

csiph-web