From: Joerg Roedel <jroedel-l3A5Bk7waGM@public.gmane.org>
To: kbuild test robot <lkp-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kbuild-all-JC7UmRfGjtg@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/2] iommu/vt-d: Fix crash when accessing VT-d sysfs entries
Date: Wed, 1 Mar 2017 11:01:26 +0100 [thread overview]
Message-ID: <20170301100126.GP4154@suse.de> (raw)
In-Reply-To: <201703010825.4Q2UVVIO%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
On Wed, Mar 01, 2017 at 08:19:30AM +0800, kbuild test robot wrote:
> >> include/linux/intel-iommu.h:457:52: error: 'struct iommu_device' has no member named 'dev'
> return container_of(dev, struct intel_iommu, iommu.dev);
Yeah, I noticed that issue too and fixed it before sending the
pull-request.
Thanks,
Joerg
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <jroedel@suse.de>
To: kbuild test robot <lkp@intel.com>
Cc: Joerg Roedel <joro@8bytes.org>,
kbuild-all@01.org, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] iommu/vt-d: Fix crash when accessing VT-d sysfs entries
Date: Wed, 1 Mar 2017 11:01:26 +0100 [thread overview]
Message-ID: <20170301100126.GP4154@suse.de> (raw)
In-Reply-To: <201703010825.4Q2UVVIO%fengguang.wu@intel.com>
On Wed, Mar 01, 2017 at 08:19:30AM +0800, kbuild test robot wrote:
> >> include/linux/intel-iommu.h:457:52: error: 'struct iommu_device' has no member named 'dev'
> return container_of(dev, struct intel_iommu, iommu.dev);
Yeah, I noticed that issue too and fixed it before sending the
pull-request.
Thanks,
Joerg
next prev parent reply other threads:[~2017-03-01 10:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 14:10 [PATCH 1/2] iommu/vt-d: Fix crash when accessing VT-d sysfs entries Joerg Roedel
2017-02-28 14:10 ` Joerg Roedel
[not found] ` <1488291019-13836-1-git-send-email-joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-02-28 14:10 ` [PATCH 2/2] iommu/amd: Fix crash when accessing AMD-Vi " Joerg Roedel
2017-02-28 14:10 ` Joerg Roedel
2017-03-01 0:19 ` [PATCH 1/2] iommu/vt-d: Fix crash when accessing VT-d " kbuild test robot
2017-03-01 0:19 ` kbuild test robot
[not found] ` <201703010825.4Q2UVVIO%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-03-01 10:01 ` Joerg Roedel [this message]
2017-03-01 10:01 ` Joerg Roedel
2017-03-01 1:06 ` kbuild test robot
2017-03-01 1:06 ` kbuild test robot
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=20170301100126.GP4154@suse.de \
--to=jroedel-l3a5bk7wagm@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=kbuild-all-JC7UmRfGjtg@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lkp-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/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.