From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Michael Roth <michael.roth@amd.com>,
Dionna Glaze <dionnaglaze@google.com>,
Brijesh Singh <brijesh.singh@amd.com>,
Ashish Kalra <ashish.kalra@amd.com>,
Peter Gonda <pgonda@google.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] crypto: ccp: Fix sev_issue_cmd code block
Date: Sun, 4 Feb 2024 20:34:04 +0700 [thread overview]
Message-ID: <9a114575-3a76-4d58-9770-804e00e0ccdd@gmail.com> (raw)
In-Reply-To: <20240204112626.GBZb90Yl5ps7awXOZT@fat_crate.local>
On 2/4/24 18:26, Borislav Petkov wrote:
> On Sun, Feb 04, 2024 at 06:06:04PM +0700, Bagas Sanjaya wrote:
>> Stephen Rothwell reports htmldocs warnings when merging tip tree:
>>
>> Documentation/virt/coco/sev-guest.rst:75: WARNING: Inline emphasis start-string without end-string.
>> Documentation/virt/coco/sev-guest.rst:78: WARNING: Inline emphasis start-string without end-string.
>> Documentation/virt/coco/sev-guest.rst:81: WARNING: Inline emphasis start-string without end-string.
>> Documentation/virt/coco/sev-guest.rst:83: WARNING: Definition list ends without a blank line; unexpected unindent.
>>
>> sev_issue_cmd struct code block has unindented block marker, hence above
>> warnings. Fix the marker by appending it instead at the end of preceding
>> paragraph to silence these warnings.
>>
>> Fixes: f5db8841ebe59d ("crypto: ccp: Add the SNP_PLATFORM_STATUS command")
>> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
>> Closes: https://lore.kernel.org/linux-next/20240202145932.31c62fd6@canb.auug.org.au/
>> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
>> ---
>> Documentation/virt/coco/sev-guest.rst | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> https://git.kernel.org/tip/1bfca8d2800ab5ef0dfed335a2a29d1632c99411
>
Oops, I didn't see that commit when I was submitting. Thanks
anyway.
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2024-02-04 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 11:06 [PATCH] crypto: ccp: Fix sev_issue_cmd code block Bagas Sanjaya
2024-02-04 11:26 ` Borislav Petkov
2024-02-04 13:34 ` Bagas Sanjaya [this message]
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=9a114575-3a76-4d58-9770-804e00e0ccdd@gmail.com \
--to=bagasdotme@gmail.com \
--cc=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=corbet@lwn.net \
--cc=dionnaglaze@google.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pgonda@google.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@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