From: Akira Yokosawa <akiyks@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Lars Ellenberg <lars.ellenberg@linbit.com>,
drbd-dev@lists.linbit.com, linux-kernel@vger.kernel.org,
Philipp Reisner <philipp.reisner@linbit.com>,
linux-doc@vger.kernel.org
Subject: Re: [Drbd-dev] [PATCH] docs: admin-guide/blockdev: Use subgraphs in node-states-8.dot
Date: Thu, 25 Nov 2021 23:16:48 +0900 [thread overview]
Message-ID: <3c0ffc75-0e0f-1701-267b-1bedb6481b79@gmail.com> (raw)
In-Reply-To: <3cbff170-582b-b6cf-0988-e0d0c9b47505@gmail.com>
On Wed, 17 Nov 2021 18:38:14 +0900, Akira Yokosawa wrote:
> While node-states-8.dot has two digraphs, dot(1) command can not
> properly handle multiple graphs in a DOT file.
>
> Use subgraphs and merge them into a single graph.
>
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
> Cc: Philipp Reisner <philipp.reisner@linbit.com>
> Cc: Lars Ellenberg <lars.ellenberg@linbit.com>
> ---
> Hi Jon,
>
> I happened to spot a broken DOT script at the bottom of
>
> https://www.kernel.org/doc/html/latest/admin-guide/blockdev/drbd/figures.html
>
> and managed to fix it.
Gentle ping?
Thanks, Akira
>
> DRBD DRIVER maintainers,
> If I'm missing something here, please let me know.
>
> Thanks, Akira
> --
> .../blockdev/drbd/node-states-8.dot | 25 +++++++++++--------
> 1 file changed, 14 insertions(+), 11 deletions(-)
>
> diff --git a/Documentation/admin-guide/blockdev/drbd/node-states-8.dot b/Documentation/admin-guide/blockdev/drbd/node-states-8.dot
> index bfa54e1f8016..993f0c152ead 100644
> --- a/Documentation/admin-guide/blockdev/drbd/node-states-8.dot
> +++ b/Documentation/admin-guide/blockdev/drbd/node-states-8.dot
> @@ -1,13 +1,16 @@
> -digraph node_states {
> - Secondary -> Primary [ label = "ioctl_set_state()" ]
> - Primary -> Secondary [ label = "ioctl_set_state()" ]
> -}
> +digraph G {
> + compound=true;
> + subgraph node_states {
> + Secondary -> Primary [ label = "ioctl_set_state()" ]
> + Primary -> Secondary [ label = "ioctl_set_state()" ]
> + }
>
> -digraph peer_states {
> - Secondary -> Primary [ label = "recv state packet" ]
> - Primary -> Secondary [ label = "recv state packet" ]
> - Primary -> Unknown [ label = "connection lost" ]
> - Secondary -> Unknown [ label = "connection lost" ]
> - Unknown -> Primary [ label = "connected" ]
> - Unknown -> Secondary [ label = "connected" ]
> + subgraph peer_states {
> + Secondary -> Primary [ label = "recv state packet" ]
> + Primary -> Secondary [ label = "recv state packet" ]
> + Primary -> Unknown [ label = "connection lost" ]
> + Secondary -> Unknown [ label = "connection lost" ]
> + Unknown -> Primary [ label = "connected" ]
> + Unknown -> Secondary [ label = "connected" ]
> + }
> }
>
> base-commit: 53b606fa29e321352a105978726b975b42b292a4
>
next prev parent reply other threads:[~2021-11-25 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 9:38 [Drbd-dev] [PATCH] docs: admin-guide/blockdev: Use subgraphs in node-states-8.dot Akira Yokosawa
2021-11-25 14:16 ` Akira Yokosawa [this message]
2021-11-25 17:41 ` Joel Colledge
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=3c0ffc75-0e0f-1701-267b-1bedb6481b79@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=drbd-dev@lists.linbit.com \
--cc=lars.ellenberg@linbit.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philipp.reisner@linbit.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