From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Jiri Pirko <jiri@resnulli.us>, Jonathan Corbet <corbet@lwn.net>,
"David S. Miller" <davem@davemloft.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Networking <netdev@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH 0/2] Documentation fixes for dpll subsystem
Date: Mon, 18 Sep 2023 16:32:37 +0700 [thread overview]
Message-ID: <20230918093240.29824-1-bagasdotme@gmail.com> (raw)
First of all, sorry for not reviewing dpll series [1] before it gets merged. I
was prompted to post this doc fixup mini series because I was emailed by kernel
test robot (see [1/2] for the warnings).
This fixup is all code block related.
[1]: https://lore.kernel.org/netdev/20230913204943.1051233-1-vadim.fedorenko@linux.dev/
Bagas Sanjaya (2):
Documentation: dpll: Fix code blocks
Documentation: dpll: wrap DPLL_CMD_PIN_GET output in a code block
Documentation/driver-api/dpll.rst | 27 +++++++++++++++------------
1 file changed, 15 insertions(+), 12 deletions(-)
base-commit: 8d6198a14e2bfb09f190055b387c90b4ac9b49a4
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2023-09-18 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 9:32 Bagas Sanjaya [this message]
2023-09-18 9:32 ` [PATCH 1/2] Documentation: dpll: Fix code blocks Bagas Sanjaya
2023-09-18 10:01 ` Vadim Fedorenko
2023-09-18 9:32 ` [PATCH 2/2] Documentation: dpll: wrap DPLL_CMD_PIN_GET output in a code block Bagas Sanjaya
2023-09-18 10:03 ` Vadim Fedorenko
2023-09-18 10:04 ` [PATCH 0/2] Documentation fixes for dpll subsystem Vadim Fedorenko
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=20230918093240.29824-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vadim.fedorenko@linux.dev \
/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).