From: Joerg Roedel <joro@8bytes.org>
To: Brian Masney <masneyb@onstation.org>
Cc: robdclark@gmail.com, bjorn.andersson@linaro.org,
agross@kernel.org, iommu@lists.linux-foundation.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH] iommu/qcom: fix NULL pointer dereference during probe deferral
Date: Tue, 7 Jan 2020 16:44:29 +0100 [thread overview]
Message-ID: <20200107154429.GE30750@8bytes.org> (raw)
In-Reply-To: <20200107140013.GA9084@onstation.org>
On Tue, Jan 07, 2020 at 09:00:14AM -0500, Brian Masney wrote:
> On Tue, Jan 07, 2020 at 02:25:30PM +0100, Joerg Roedel wrote:
> > On Tue, Dec 31, 2019 at 10:39:49PM -0500, Brian Masney wrote:
> > > drivers/iommu/qcom_iommu.c | 12 ++++++++++--
> > > 1 file changed, 10 insertions(+), 2 deletions(-)
> >
> > Shortened commit-message a bit and applied for v5.5, thanks.
>
> You might want to hold off on applying this since it looks like Robin
> Murphy has a better fix.
>
> https://lore.kernel.org/lkml/fc055443-8716-4a0e-b4d5-311517d71ea0@arm.com/
Alright, thanks for the heads-up. I dropped that patch from my fixes
branch.
Regards,
Joerg
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Brian Masney <masneyb@onstation.org>
Cc: linux-arm-msm@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, agross@kernel.org,
bjorn.andersson@linaro.org, Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH] iommu/qcom: fix NULL pointer dereference during probe deferral
Date: Tue, 7 Jan 2020 16:44:29 +0100 [thread overview]
Message-ID: <20200107154429.GE30750@8bytes.org> (raw)
In-Reply-To: <20200107140013.GA9084@onstation.org>
On Tue, Jan 07, 2020 at 09:00:14AM -0500, Brian Masney wrote:
> On Tue, Jan 07, 2020 at 02:25:30PM +0100, Joerg Roedel wrote:
> > On Tue, Dec 31, 2019 at 10:39:49PM -0500, Brian Masney wrote:
> > > drivers/iommu/qcom_iommu.c | 12 ++++++++++--
> > > 1 file changed, 10 insertions(+), 2 deletions(-)
> >
> > Shortened commit-message a bit and applied for v5.5, thanks.
>
> You might want to hold off on applying this since it looks like Robin
> Murphy has a better fix.
>
> https://lore.kernel.org/lkml/fc055443-8716-4a0e-b4d5-311517d71ea0@arm.com/
Alright, thanks for the heads-up. I dropped that patch from my fixes
branch.
Regards,
Joerg
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-01-07 15:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 3:39 [PATCH] iommu/qcom: fix NULL pointer dereference during probe deferral Brian Masney
2020-01-01 3:39 ` Brian Masney
2020-01-01 11:44 ` Stephan Gerhold
2020-01-01 11:44 ` Stephan Gerhold
2020-01-01 18:18 ` Jonathan Neuschäfer
2020-01-01 18:18 ` Jonathan Neuschäfer
2020-01-07 13:25 ` Joerg Roedel
2020-01-07 13:25 ` Joerg Roedel
2020-01-07 14:00 ` Brian Masney
2020-01-07 14:00 ` Brian Masney
2020-01-07 15:44 ` Joerg Roedel [this message]
2020-01-07 15:44 ` Joerg Roedel
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=20200107154429.GE30750@8bytes.org \
--to=joro@8bytes.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masneyb@onstation.org \
--cc=robdclark@gmail.com \
--cc=robin.murphy@arm.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 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.