On Thu, Jan 23, 2025, Kevin Loughlin wrote: > v5: > - explicitly encode wbnoinvd as 0xf3 0x0f 0x09 for binutils backwards compatibility Please, please, please do not send new series with In-Reply-To. Trying to sort through the different versions in my workflow was painful. From Documentation/process/maintainer-kvm-x86.rst: Links ~~~~~ Do not explicitly reference bug reports, prior versions of a patch/series, etc. via ``In-Reply-To:`` headers. Using ``In-Reply-To:`` becomes an unholy mess for large series and/or when the version count gets high, and ``In-Reply-To:`` is useless for anyone that doesn't have the original message, e.g. if someone wasn't Cc'd on the bug report or if the list of recipients changes between versions. To link to a bug report, previous version, or anything of interest, use lore links. For referencing previous version(s), generally speaking do not include a Link: in the changelog as there is no need to record the history in git, i.e. put the link in the cover letter or in the section git ignores. Do provide a formal Link: for bug reports and/or discussions that led to the patch. The context of why a change was made is highly valuable for future readers.
