From: patchwork-bot+netdevbpf@kernel.org
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, linux-pm@vger.kernel.org,
bpf@vger.kernel.org, corbet@lwn.net, ray.huang@amd.com,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, pbonzini@redhat.com,
thomas.lendacky@amd.com, davemarchevsky@fb.com,
perry.yuan@amd.com, rafael.j.wysocki@intel.com,
wyes.karny@amd.com, mario.limonciello@amd.com,
oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 0/3] Documentation fixes for next-20230215
Date: Wed, 15 Feb 2023 16:50:17 +0000 [thread overview]
Message-ID: <167647981714.6958.9219328838471519095.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230215123253.41552-1-bagasdotme@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 15 Feb 2023 19:32:50 +0700 you wrote:
> Here are fixes for documentation (htmldocs) warnings as reported for
> next-20230215. The changelog below should be self-explanatory.
>
> Each patch can be applied separately by respective maintainers.
>
> Bagas Sanjaya (3):
> Documentation: hw-vuln: Wrap mitigate_smt_rsb example in literal code
> block
> Documentation: bpf: Add missing line break separator in node_data
> struct code block
> Documentation: amd-pstate: disambiguate user space sections
>
> [...]
Here is the summary with links:
- [1/3] Documentation: hw-vuln: Wrap mitigate_smt_rsb example in literal code block
(no matching commit)
- [2/3] Documentation: bpf: Add missing line break separator in node_data struct code block
https://git.kernel.org/bpf/bpf-next/c/e2d323a1f009
- [3/3] Documentation: amd-pstate: disambiguate user space sections
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-02-15 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 12:32 [PATCH 0/3] Documentation fixes for next-20230215 Bagas Sanjaya
2023-02-15 12:32 ` [PATCH 1/3] Documentation: hw-vuln: Wrap mitigate_smt_rsb example in literal code block Bagas Sanjaya
2023-02-15 12:32 ` [PATCH 2/3] Documentation: bpf: Add missing line break separator in node_data struct " Bagas Sanjaya
2023-02-15 16:46 ` Alexei Starovoitov
2023-02-15 12:32 ` [PATCH 3/3] Documentation: amd-pstate: disambiguate user space sections Bagas Sanjaya
2023-02-15 13:52 ` Wyes Karny
2023-02-15 14:20 ` Huang Rui
2023-02-15 14:59 ` Rafael J. Wysocki
2023-02-15 16:50 ` patchwork-bot+netdevbpf [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=167647981714.6958.9219328838471519095.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=davemarchevsky@fb.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=martin.lau@linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pbonzini@redhat.com \
--cc=perry.yuan@amd.com \
--cc=rafael.j.wysocki@intel.com \
--cc=ray.huang@amd.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=wyes.karny@amd.com \
--cc=yhs@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.