From: Alexander Duyck <alexander.h.duyck@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Guenter Roeck <linux@roeck-us.net>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux-Next <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:INTEL IOMMU (VT-d)" <iommu@lists.linux-foundation.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Robin Murphy <robin.murphy@arm.com>,
Greg KH <gregkh@linuxfoundation.org>,
Linus PPC <linuxppc-dev@lists.ozlabs.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: linux-next: Tree for Oct 4
Date: Fri, 5 Oct 2018 07:27:29 -0700 [thread overview]
Message-ID: <72f64b32-20f0-0e9a-a8f6-3e0845abb586@linux.intel.com> (raw)
In-Reply-To: <20181005153905.126a005e@canb.auug.org.au>
On 10/4/2018 10:39 PM, Stephen Rothwell wrote:
> Hi Guenter,
>
> On Thu, 4 Oct 2018 18:33:02 -0700 Guenter Roeck <linux@roeck-us.net> wrote:
>>
>> Most of the boot failures are hopefully fixed with
>> https://lore.kernel.org/patchwork/patch/995254/
>
> I have added that commit to linux-next today.
>
After getting over that I ended up running into an issues with a NULL
pointer dereference updating static keys/jump labels that was fixed by:
https://lore.kernel.org/patchwork/patch/993864/
Thanks.
- Alex
next prev parent reply other threads:[~2018-10-05 14:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 8:34 Stephen Rothwell
2018-10-04 13:46 ` Guenter Roeck
2018-10-04 14:21 ` Geert Uytterhoeven
2018-10-04 23:44 ` Stephen Rothwell
2018-10-05 1:33 ` Guenter Roeck
2018-10-05 5:39 ` Stephen Rothwell
2018-10-05 14:27 ` Alexander Duyck [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-04 5:55 Stephen Rothwell
2023-10-04 5:21 Stephen Rothwell
2022-10-04 11:05 Stephen Rothwell
2019-10-04 5:59 Stephen Rothwell
2016-10-04 3:56 Stephen Rothwell
2016-10-04 4:22 ` Stephen Rothwell
2013-10-05 22:44 Mark Brown
2013-10-06 18:13 ` Guenter Roeck
2012-10-04 5:33 Stephen Rothwell
2011-10-04 8:11 Stephen Rothwell
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=72f64b32-20f0-0e9a-a8f6-3e0845abb586@linux.intel.com \
--to=alexander.h.duyck@linux.intel.com \
--cc=benh@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=robin.murphy@arm.com \
--cc=sfr@canb.auug.org.au \
/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
Powered by JetHome