Re: linux-next: build warning after merge of the iommu tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: linux-next: build warning after merge of the iommu tree
From: Joerg Roedel <joro@xxxxxxxxxx>
Date: Thu, 8 Nov 2018 10:30:30 +0100
Cc: Linux-Next Mailing List <linux-next@xxxxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Jacob Pan <jacob.jun.pan@xxxxxxxxxxxxxxx>, Ashok Raj <ashok.raj@xxxxxxxxx>
In-reply-to: <20181108123938.2026559e@canb.auug.org.au>
References: <20181108123938.2026559e@canb.auug.org.au>
User-agent: Mutt/1.9.4 (2018-02-28)

Hi Stephen,

On Thu, Nov 08, 2018 at 12:39:38PM +1100, Stephen Rothwell wrote:
> Introduced by commit
> 
>   248808a0fad0 ("iommu/vt-d: Respect max guest address width in agaw")

Thanks for the report! That commit was revoked by the submitter and is
now removed from the tree. The warning should disappear in the next
merge.

Regards,

	Joerg

References:
- linux-next: build warning after merge of the iommu tree
  - From: Stephen Rothwell

Prev by Date: next/pending-fixes build: 199 builds: 0 failed, 199 passed, 30 warnings (v4.20-rc1-220-gc0f0d69cd6d7)
Next by Date: Re: locks_remove_file() -> flock_lock_inode() sleeps in invalid context, false positive due to NULL dereference ?
Previous by thread: linux-next: build warning after merge of the iommu tree
Next by thread: linux-next: build warning after merge of the iommu tree
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel] [Linux USB Development] [Yosemite News] [Linux SCSI]

Powered by Linux