linux-kernel - Re: linux-next: build failure after merge of the sound-asoc tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 30 Oct 2012 07:46:31 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Liam Girdwood <lrg@...com>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the sound-asoc tree

Hi Mark,

On Mon, 29 Oct 2012 18:15:34 +0000 Mark Brown <broonie@...nsource.wolfsonmicro.com> wrote:
>
> Honestly when I'm travelling with the automated build testing Fenguang
> and friends are doing it's actually faster to just push things up rather
> than doing testing of branches like this locally, their build farm
> usually kicks in very close to the time it takes me to do a single fresh
> build.

Then you need to have a different branch being tested by Fenguang and
friends to what you have in linux-next.   The stuff that you put into
linux-next has to be at least build tested, so you should delay pushing
it up to your linux-next included branch until after that is done.

This case was particularly irritating because you were the developer of
the patch that was broken which indicates that you are not even testing
your own development work before pushing it out for others to work on top
of.
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped