>-----Original Message----- >From: Eric Auger <eric.auger@xxxxxxxxxx> >Sent: Wednesday, September 20, 2023 7:05 PM >Subject: Re: [PATCH v1 02/22] Update linux-header to support iommufd cdev and >hwpt alloc > > > >On 9/15/23 05:02, Duan, Zhenzhong wrote: >> Hi Eric, >> >>> -----Original Message----- >>> From: Eric Auger <eric.auger@xxxxxxxxxx> >>> Sent: Thursday, September 14, 2023 10:46 PM >>> Subject: Re: [PATCH v1 02/22] Update linux-header to support iommufd cdev >and >>> hwpt alloc >>> >>> Hi Zhenzhong, >>> >>> On 8/30/23 12:37, Zhenzhong Duan wrote: >>>> From https://git.kernel.org/pub/scm/linux/kernel/git/jgg/iommufd.git >>>> branch: for_next >>>> commit id: eb501c2d96cfce6b42528e8321ea085ec605e790 >>> I see that in your branch you have now updated against v6.6-rc1. However >>> you should run a full ./scripts/update-linux-headers.sh, >>> ie. not only importing the changes in linux-headers/linux/iommufd.h as >>> it seems to do but also import all changes brought with this linux version. >> Found reason. The base is already against v6.6-rc1, [PATCH v1 01/22] added >> Iommufd.h into script and this patch added it. >> I agree the subject is confusing, need to be like "Update iommufd.h to linux- >header" >> I'll fix the subject in next version, thanks for point out. > >OK I see >da3c22c74a3c linux-headers: Update to Linux v6.6-rc1 (8 days ago) ><Thomas Huth> >now. So you need to add the sha1 against which you ran >./scripts/update-linux-headers.sh and in that case you can precise that >given [PATCH v1 01/22] scripts/update-linux-headers: Add iommufd.h added >iommufd export and given Thomas' patch, only >iommufd.h is added. Sure, will make it clear in v2. Thanks Zhenzhong
