From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Freedesktop DRI List <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux KVM <kvm@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Oded Gabbay <ogabbay@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Paolo Bonzini <pbonzini@redhat.com>,
Jeffrey Hugo <quic_jhugo@quicinc.com>,
Ofir Bitton <obitton@habana.ai>,
Sean Christopherson <seanjc@google.com>,
Aaron Lewis <aaronlewis@google.com>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH linux-next 0/3] Documentation fixes for linux-next (Jan 20)
Date: Fri, 20 Jan 2023 19:35:31 +0700 [thread overview]
Message-ID: <20230120123534.137413-1-bagasdotme@gmail.com> (raw)
Here are fixes for recent htmldocs warnings reported in linux-next. Each
patches can be picked up separately if ACKed.
Bagas Sanjaya (3):
Documentation: accel: escape wildcard in special file path
habanalabs: Fix list of /sys/class/habanalabs/hl<n>/status
kvm: x86/pmu: Add blank line separator before
KVM_CAP_PMU_EVENT_MASKED_EVENTS code path list
.../ABI/testing/sysfs-driver-habanalabs | 23 ++++++++++---------
Documentation/accel/introduction.rst | 6 ++---
Documentation/virt/kvm/api.rst | 1 +
3 files changed, 16 insertions(+), 14 deletions(-)
base-commit: d514392f17fd4d386cfadde7f849d97db4ca1fb0
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2023-01-20 12:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 12:35 Bagas Sanjaya [this message]
2023-01-20 12:35 ` [PATCH linux-next 1/3] Documentation: accel: escape wildcard in special file path Bagas Sanjaya
2023-01-20 14:59 ` Jeffrey Hugo
2023-01-22 9:35 ` Oded Gabbay
2023-01-20 12:35 ` [PATCH linux-next 2/3] habanalabs: Fix list of /sys/class/habanalabs/hl<n>/status Bagas Sanjaya
2023-01-22 9:37 ` Oded Gabbay
2023-01-20 12:35 ` [PATCH linux-next 3/3] kvm: x86/pmu: Add blank line separator before KVM_CAP_PMU_EVENT_MASKED_EVENTS code path list Bagas Sanjaya
2023-01-20 18:04 ` Sean Christopherson
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=20230120123534.137413-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=aaronlewis@google.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=obitton@habana.ai \
--cc=ogabbay@kernel.org \
--cc=pbonzini@redhat.com \
--cc=quic_jhugo@quicinc.com \
--cc=seanjc@google.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