linux-kernel - Re: linux-next: build failure after merge of the battery 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]

Message-ID: <20120327130350.GB7972@lizard>
Date:	Tue, 27 Mar 2012 17:03:50 +0400
From:	Anton Vorontsov <cbouatmailru@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Arun Murthy <arun.murthy@...ricsson.com>,
	Linus Walleij <linus.walleij@...aro.org>,
	Samuel Ortiz <sameo@...ux.intel.com>
Subject: Re: linux-next: build failure after merge of the battery tree

On Tue, Mar 27, 2012 at 08:44:14AM +1100, Stephen Rothwell wrote:
> Hi Anton,
> 
> On Mon, 26 Mar 2012 20:11:32 +0400 Anton Vorontsov <cbouatmailru@...il.com> wrote:
> >
> > I pulled my current battery tree into next-20120326, and I can't reproduce
> > the issue (using allmodconfig on x86_64).
> 
> I have moved the battery tree to after the mfd tree in my merge sequence
> so we will see if that helps.  I really hate having ordering dependencies
> in linux-next (since they change over time and people have to remember to
> tell me and to send stuff to Linus in the right order).  Also, it means
> that you are not testing exactly what you are sending to me - I assume
> that your testing must be including the mfd tree somehow.
> 
> These sort of things should be fixed by having the common code in a
> separate (stable) branch that is merged into both trees.  Or in some
> cases by merely cherry-picking a very small number of commits from one
> tree to the other.

Yes, I was thinking about cherry-picking a few MFD patches, but
decided not to as the driver is quite big and completely new, so
it would have some glitches anyway, and thus would need fixups.
One less, one more.

But for such drivers I usually give my 'Acked-by' so that
patches could be merged via single tree (i.e. mfd). But nobody
asked me in this case.

Thanks,

-- 
Anton Vorontsov
Email: cbouatmailru@...il.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/