Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Cc:     baolu.lu@linux.intel.com, iommu@lists.linux-foundation.org,
        linux-kernel@vger.kernel.org,
        Roland Dreier <roland@purestorage.com>,
        Jim Yan <jimyan@baidu.com>
Subject: Re: [PATCH 1/1] iommu/vt-d: Add a quirk flag for scope mismatched
 devices
To:     Joerg Roedel <joro@8bytes.org>
References: <20191224062240.4796-1-baolu.lu@linux.intel.com>
From:   Lu Baolu <baolu.lu@linux.intel.com>
Message-ID: <dec66878-9bd7-70cb-9b53-d8f4a6230916@linux.intel.com>
Date:   Thu, 2 Jan 2020 07:36:22 +0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <20191224062240.4796-1-baolu.lu@linux.intel.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On 12/24/19 2:22 PM, Lu Baolu wrote:
> We expect devices with endpoint scope to have normal PCI headers,
> and devices with bridge scope to have bridge PCI headers.  However
> Some PCI devices may be listed in the DMAR table with bridge scope,
> even though they have a normal PCI header. Add a quirk flag for
> those special devices.
> 
> Cc: Roland Dreier<roland@purestorage.com>
> Cc: Jim Yan<jimyan@baidu.com>
> Signed-off-by: Lu Baolu<baolu.lu@linux.intel.com>

Queued for v5.6.

Thanks,
-baolu