From: Marc Zyngier <maz@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christoffer Dall <cdall@cs.columbia.edu>,
Jianyong Wu <jianyong.wu@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the kvm-arm tree
Date: Thu, 08 Apr 2021 15:35:20 +0100 [thread overview]
Message-ID: <87wntcondj.wl-maz@kernel.org> (raw)
In-Reply-To: <20210408214400.52632f7d@canb.auug.org.au>
On Thu, 08 Apr 2021 12:44:00 +0100,
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> [1 <text/plain; US-ASCII (quoted-printable)>]
> Hi all,
>
> After merging the kvm-arm tree, today's linux-next build (htmldocs)
> produced this warning:
>
> /home/sfr/next/next/Documentation/virt/kvm/arm/ptp_kvm.rst:19: WARNING: Malformed table.
> Text in column margin in table line 5.
>
> ============= ========== ==========
> Function ID: (uint32) 0x86000001
> Arguments: (uint32) KVM_PTP_VIRT_COUNTER(0)
> KVM_PTP_PHYS_COUNTER(1)
> Return Values: (int32) NOT_SUPPORTED(-1) on error, or
> (uint32) Upper 32 bits of wall clock time (r0)
> (uint32) Lower 32 bits of wall clock time (r1)
> (uint32) Upper 32 bits of counter (r2)
> (uint32) Lower 32 bits of counter (r3)
> Endianness: No Restrictions.
> ============= ========== ==========
>
> Introduced by commit
>
> 3bf725699bf6 ("KVM: arm64: Add support for the KVM PTP service")
Now fixed, thanks.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2021-04-08 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 11:44 linux-next: build warning after merge of the kvm-arm tree Stephen Rothwell
2021-04-08 14:35 ` Marc Zyngier [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-04 10:56 Stephen Rothwell
2022-05-04 12:18 ` Marc Zyngier
2020-10-02 8:41 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=87wntcondj.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=cdall@cs.columbia.edu \
--cc=jianyong.wu@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).