From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Michael Ellerman <mpe@ellerman•id.au>
Cc: Abdul Haleem <abdhalee@linux•vnet.ibm.com>,
linuxppc-dev <linuxppc-dev@lists•ozlabs.org>,
linux-kernel <linux-kernel@vger•kernel.org>,
linux-input@vger•kernel.org, Jiri Kosina <jikos@kernel•org>,
Benjamin Tissoires <benjamin.tissoires@redhat•com>,
sachinp <sachinp@linux•vnet.ibm.com>,
Rob Landley <rob@landley•net>,
Andrew Morton <akpm@linux-foundation•org>
Subject: Re: [linux-next] PPC Lpar fail to boot with error hid: module verification failed: signature and/or required key missing - tainting kernel
Date: Fri, 26 May 2017 07:24:37 +1000 [thread overview]
Message-ID: <20170526072437.46499fbd@canb.auug.org.au> (raw)
In-Reply-To: <8760gp9jjl.fsf@concordia.ellerman.id.au>
Hi Michael,
On Thu, 25 May 2017 23:02:06 +1000 Michael Ellerman <mpe@ellerman•id.au> wrote:
>
> It'll be:
>
> ee35011fd032 ("initramfs: make initramfs honor CONFIG_DEVTMPFS_MOUNT")
And Andrew has asked me to drop that patch from linux-next which will
happen today.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2017-05-25 21:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 8:29 [linux-next] PPC Lpar fail to boot with error hid: module verification failed: signature and/or required key missing - tainting kernel Abdul Haleem
2017-05-25 9:08 ` Jiri Kosina
2017-05-25 13:02 ` Michael Ellerman
2017-05-25 21:24 ` Stephen Rothwell [this message]
2017-05-26 6:24 ` Rob Landley
2017-05-29 5:06 ` Michael Ellerman
2017-09-13 23:51 ` [PATCH v3] Make initramfs honor CONFIG_DEVTMPFS_MOUNT Rob Landley
2017-09-14 9:17 ` Christophe LEROY
2017-09-17 4:03 ` Rob Landley
2017-09-17 13:51 ` Henrique de Moraes Holschuh
2017-09-20 3:29 ` Rob Landley
2017-09-21 10:13 ` Michael Ellerman
2017-09-14 17:45 ` Greg KH
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=20170526072437.46499fbd@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=abdhalee@linux$(echo .)vnet.ibm.com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=benjamin.tissoires@redhat$(echo .)com \
--cc=jikos@kernel$(echo .)org \
--cc=linux-input@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=rob@landley$(echo .)net \
--cc=sachinp@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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