[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <511C6952.10802@zytor.com>
Date: Wed, 13 Feb 2013 20:34:26 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
CC: Andrew Morton <akpm@...ux-foundation.org>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>,
Peter Zijlstra <peterz@...radead.org>,
Dagfinn Ilmari Mannsåker
<ilmari@...ari.org>
Subject: Re: linux-next: manual merge of the akpm tree with the tip tree
On 02/13/2013 08:25 PM, Stephen Rothwell wrote:
> Hi Andrew,
>
> Today's linux-next merge of the akpm tree got a conflict in
> kernel/timeconst.pl between commit 63a3f603413f ("timeconst.pl: Eliminate
> Perl warning") from the tip tree and commit "timeconst.pl: remove
> deprecated defined(@array)" from the akpm tree.
>
> These both fix the same problem, I arbitrarily chose the akpm tree version.
>
I should try to resurrect the bc version (which doesn't need the canning
junk, bc being the POSIX tool for arbitrary-precision arithmetic.)
There was an error on one of akpm's machines long ago which confused the
bcrap out of us, because bc hadn't changed, but recently someone pointed
to a bug in *make* (relating to pipes) from around that era which would
have explained (a) the failure, and (b) why it only hit one box even
though bc was the exact same version.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
--
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/
Powered by blists - more mailing lists