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;
MIME-Version: 1.0
References: <CAHmME9qTA90=GEr6h1GZh0CjS+6tpe5uuqkYoJVv79h0zd0w1w@mail.gmail.com>
 <20220719130207.147536-1-Jason@zx2c4.com> <7285be49c459bdc8f4ec3abe85d9e171@linux.ibm.com>
In-Reply-To: <7285be49c459bdc8f4ec3abe85d9e171@linux.ibm.com>
From:   "Jason A. Donenfeld" <Jason@zx2c4.com>
Date:   Mon, 1 Aug 2022 16:50:00 +0200
Message-ID: <CAHmME9rk27DA0DmTY7hhedFT0ftkMKhZn30NCvjkkzkKD0hNfQ@mail.gmail.com>
Subject: Re: [PATCH v3] random: handle archrandom with multiple longs
To:     freude@linux.ibm.com
Cc:     linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
        linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
        x86@kernel.org, Will Deacon <will@kernel.org>,
        Alexander Gordeev <agordeev@linux.ibm.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        "H . Peter Anvin" <hpa@zytor.com>,
        Catalin Marinas <catalin.marinas@arm.com>,
        Borislav Petkov <bp@suse.de>,
        Heiko Carstens <hca@linux.ibm.com>,
        Johannes Berg <johannes@sipsolutions.net>,
        Mark Rutland <mark.rutland@arm.com>,
        Michael Ellerman <mpe@ellerman.id.au>,
        Stephen Rothwell <sfr@canb.auug.org.au>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Hi Harald,

On Mon, Aug 1, 2022 at 4:47 PM Harald Freudenberger
<freude@linux.ibm.com> wrote:
>
> Nice interface :-)
> Here is my
> Acked-by: Harald Freudenberger <freude@linux.ibm.com>

You're too late; I already sent in my pull request. But that's okay; I
received Heiko's ack on this for s390.

> but please keep in mind that your patch does not apply cleanly as there
> is my other patch
> 918e75f77af7 ("s390/archrandom: prevent CPACF trng invocations in
> interrupt context")
> in between.

Yea, this was a late addition to 5.19, and my random tree was based on
an earlier rc of 5.19. That kind of thing happens and is fine; Stephen
caught it when doing the next merge and carries the merge conflict
resolution there. I mentioned it to Linus in my pull, so he'll be able
to work it out.

Jason