[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190213115905.f8b0f189c4196eac2ca1138f@linux-foundation.org>
Date: Wed, 13 Feb 2019 11:59:05 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
"H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Mark Rutland <mark.rutland@....com>
Subject: Re: linux-next: manual merge of the akpm tree with the tip tree
On Wed, 13 Feb 2019 17:49:28 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi all,
>
> Today's linux-next merge of the akpm tree got a conflict in:
>
> scripts/atomic/check-atomics.sh
>
> between commit:
>
> 4ad119545d78 ("locking/atomics: Check atomic headers with sha1sum")
>
> from the tip tree and patch:
>
> "scripts/atomic/check-atomics.sh: don't assume that scripts are executable"
>
> from the akpm tree.
>
> I fixed it up (this latter patch is now needed against the new
> scripts/atomic/gen-atomics.sh instead) and can carry the fix as
> necessary.
Thanks. I don't know why I've been carrying that fix for so long :(
Shall resend.
Powered by blists - more mailing lists