From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Joerg Roedel <joro@8bytes.org>
Cc: Vasant Hegde <vasant.hegde@amd.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Signed-off-by missing for commit in the iommu tree
Date: Mon, 27 Jun 2022 08:41:15 +1000 [thread overview]
Message-ID: <20220627084115.559a257f@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1552 bytes --]
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.
What is really happening here is that the iommu@lists.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.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-06-26 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 22:41 Stephen Rothwell [this message]
2022-07-04 11:25 ` linux-next: Signed-off-by missing for commit in the iommu tree Vasant Hegde
2022-07-06 9:25 ` Joerg Roedel
2022-07-06 11:51 ` Vasant Hegde
-- strict thread matches above, loose matches on Subject: below --
2022-03-06 20:32 Stephen Rothwell
2021-06-07 23:10 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220627084115.559a257f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=vasant.hegde@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).