public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Sachin Sant <sachinp@linux.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	linux-crypto@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [6.1.0-rc4-next-20221108] Boot failure on powerpc
Date: Wed, 9 Nov 2022 10:55:10 +0100	[thread overview]
Message-ID: <Y2t4/sELkmB4pn2p@zx2c4.com> (raw)
In-Reply-To: <E051ACF6-5282-49D1-9C60-BB2450569268@linux.ibm.com>

Should be fixed already in today's next.

  reply	other threads:[~2022-11-09  9:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09  7:09 [6.1.0-rc4-next-20221108] Boot failure on powerpc Sachin Sant
2022-11-09  9:55 ` Jason A. Donenfeld [this message]
2022-11-09 11:04   ` Sachin Sant

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y2t4/sELkmB4pn2p@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=sachinp@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox