From mboxrd@z Thu Jan 1 00:00:00 1970 From: Baoquan He Subject: Re: linux-next: manual merge of the tip tree with the iommu tree Date: Tue, 22 Aug 2017 16:11:54 +0800 Message-ID: <20170822081154.GD12401@x1> References: <20170822135057.776f3509@canb.auug.org.au> <20170822055758.GB12401@x1> <20170822174951.52dab2d1@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20170822174951.52dab2d1@canb.auug.org.au> Sender: linux-kernel-owner@vger.kernel.org To: Stephen Rothwell Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , Joerg Roedel , Linux-Next Mailing List , Linux Kernel Mailing List , Tom Lendacky List-Id: linux-next.vger.kernel.org Hi Stephen, On 08/22/17 at 05:49pm, Stephen Rothwell wrote: > Hi Baoquan, > > On Tue, 22 Aug 2017 13:57:58 +0800 Baoquan He wrote: > > > > On 08/22/17 at 01:50pm, Stephen Rothwell wrote: > > > from the iommu tree and commit: > > > > > > 2543a786aa25 ("iommu/amd: Allow the AMD IOMMU to work with memory encryption") > > > > Could you tell where the above commit is put? I can have a look. > > > > > from the tip tree. > ^^^^^^^^^^^^^^^^^ > > The tip tree is > > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git > branch auto-latest Thanks a lot! I have commit 2543a786aa25, not sure which branch it's put in. I tried to apply it to the current tip/auto-latest, and saw the conflicts. I think your change is correct. Maybe Joerg can also help have a look. Thanks Baoquan