Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 8 Jul 2022 10:13:03 +0200
From:   Borislav Petkov <bp@suse.de>
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     Theodore Ts'o <tytso@mit.edu>,
        "Jason A. Donenfeld" <Jason@zx2c4.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@redhat.com>,
        "H. Peter Anvin" <hpa@zytor.com>,
        Peter Zijlstra <peterz@infradead.org>,
        Jonathan McDowell <noodles@fb.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the random tree with the tip tree
Message-ID: <YsfnDyOaKXA3iIj4@zn.tnic>
References: <20220708171030.135b12cd@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20220708171030.135b12cd@canb.auug.org.au>
Precedence: bulk

On Fri, Jul 08, 2022 at 05:10:30PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the random tree got conflicts in:
> 
>   arch/x86/include/uapi/asm/bootparam.h
>   arch/x86/kernel/kexec-bzimage64.c
>   arch/x86/kernel/setup.c
> 
> between commit:
> 
>   b69a2afd5afc ("x86/kexec: Carry forward IMA measurement log on kexec")
> 
> from the tip tree and commit:
> 
>   c337d5c7ec9b ("x86/setup: Use rng seeds from setup_data")

Why is a x86 patch in the random tree?

And it doesn't even have a single x86 person ack?

https://git.kernel.org/pub/scm/linux/kernel/git/crng/random.git/commit/?id=c337d5c7ec9bc1d11006fd628e99c65f08455803

This is not now the process works.

-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
(HRB 36809, AG Nürnberg)