[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84e26670-5e0f-61b8-8912-42bd048faf16@amd.com>
Date: Mon, 4 Jul 2022 16:55:28 +0530
From: Vasant Hegde <vasant.hegde@....com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Joerg Roedel <joro@...tes.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the iommu tree
Hi Joerg,
On 6/27/2022 4:11 AM, Stephen Rothwell wrote:
> Hi all,
>
> Commits
>
> 145c15624f39 ("iommu/amd: Update amd_iommu_fault structure to include PCI seg ID")
> 58f1c71a0e84 ("iommu/amd: Update device_state structure to include PCI seg ID")
> 964d21a7654c ("iommu/amd: Print PCI segment ID in error log messages")
> 58e5ca96cb16 ("iommu/amd: Flush upto last_bdf only")
> 5a903a691117 ("iommu/amd: Convert to use per PCI segment rlookup_table")
> a0eedb5738c3 ("iommu/amd: Convert to use per PCI segment irq_lookup_table")
> f1bd29bde636 ("iommu/amd: Introduce per PCI segment rlookup table size")
> d59145a5e129 ("iommu/amd: Introduce per PCI segment alias table size")
> ad967e9639e3 ("iommu/amd: Introduce per PCI segment device table size")
> 89e9f3d6219d ("iommu/amd: Introduce per PCI segment last_bdf")
> e202b39618b3 ("iommu/amd: Introduce per PCI segment unity map list")
> a42d9be7f4e9 ("iommu/amd: Introduce per PCI segment dev_data_list")
> 65ad39268837 ("iommu/amd: Introduce per PCI segment irq_lookup_table")
> ec6f20c037c8 ("iommu/amd: Introduce pci segment structure")
> 98496c13a2b6 ("iommu/amd: Update struct iommu_dev_data definition")
>
> are missing a Signed-off-by from their authors.
Sorry. I didn't realize mailing list is changing "From:" header. Will you be
fixing it in your tree -OR- do you want me to resend patches with updated
"From:" line in patches?
-Vasant
>
> What is really happening here is that the iommu@...ts.linux-foundation.org
> mailing list is changing the From: header in the email submissions.
> The solution is to either use th Reply-To: header for these mails, get
> an off list copy of the patch, or make sure that all patch submissions
> to that list have a From: line at eth start of the body.
>
Powered by blists - more mailing lists