From: Tony Lindgren <tony@atomide.com>
To: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, Joerg Roedel <jroedel@suse.de>
Subject: Regression in next-20181219 with iommu
Date: Wed, 19 Dec 2018 10:09:28 -0800 [thread overview]
Message-ID: <20181219180928.GF6707@atomide.com> (raw)
Hi all,
FYI, looks like there's an iommu regression in next-20181219
caused by commit 641fb0efbff0 ("iommu/of: Don't call
iommu_ops->add_device directly").
There's a fix being discussed at:
https://lore.kernel.org/patchwork/patch/1023860/
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, Joerg Roedel <jroedel@suse.de>
Subject: Regression in next-20181219 with iommu
Date: Wed, 19 Dec 2018 10:09:28 -0800 [thread overview]
Message-ID: <20181219180928.GF6707@atomide.com> (raw)
Hi all,
FYI, looks like there's an iommu regression in next-20181219
caused by commit 641fb0efbff0 ("iommu/of: Don't call
iommu_ops->add_device directly").
There's a fix being discussed at:
https://lore.kernel.org/patchwork/patch/1023860/
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2018-12-19 18:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 18:09 Tony Lindgren [this message]
2018-12-19 18:09 ` Regression in next-20181219 with iommu Tony Lindgren
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=20181219180928.GF6707@atomide.com \
--to=tony@atomide.com \
--cc=jroedel@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.