Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752789AbdCAKep (ORCPT ); Wed, 1 Mar 2017 05:34:45 -0500 Received: from mx2.suse.de ([195.135.220.15]:58553 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752727AbdCAKeN (ORCPT ); Wed, 1 Mar 2017 05:34:13 -0500 Date: Wed, 1 Mar 2017 11:01:26 +0100 From: Joerg Roedel To: kbuild test robot Cc: Joerg Roedel , 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 Message-ID: <20170301100126.GP4154@suse.de> References: <1488291019-13836-1-git-send-email-joro@8bytes.org> <201703010825.4Q2UVVIO%fengguang.wu@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201703010825.4Q2UVVIO%fengguang.wu@intel.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 323 Lines: 11 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