From: Bagas Sanjaya <bagasdotme@gmail.com>
To: kernel test robot <lkp@intel.com>,
Joe Stringer <joe@isovalent.com>,
bpf@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, ast@kernel.org, corbet@lwn.net,
martin.lau@linux.dev, maxtram95@gmail.com,
john.fastabend@gmail.com
Subject: Re: [PATCH bpf-next v4 2/2] docs/bpf: Add LRU internals description and graph
Date: Mon, 3 Apr 2023 10:41:27 +0700 [thread overview]
Message-ID: <ZCpK5wOI0ZEedhrr@debian.me> (raw)
In-Reply-To: <202304022107.IwHc05cs-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
On Sun, Apr 02, 2023 at 09:47:49PM +0800, kernel test robot wrote:
> All warnings (new ones prefixed by >>):
>
> >> Warning: Orthogonal edges do not currently handle edge labels. Try using xlabels.
>
Hi,
I can't reproduce the warning above. My system has graphviz 2.42.2
installed (via Debian package). What graphviz version do kernel test
robot have?
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-04-03 3:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 20:06 [PATCH bpf-next v4 1/2] docs/bpf: Add table to describe LRU properties Joe Stringer
2023-04-01 20:06 ` [PATCH bpf-next v4 2/2] docs/bpf: Add LRU internals description and graph Joe Stringer
2023-04-02 13:47 ` kernel test robot
2023-04-03 3:41 ` Bagas Sanjaya [this message]
2023-04-03 8:49 ` Maxim Mikityanskiy
2023-04-03 22:14 ` Joe Stringer
2023-04-03 3:50 ` Bagas Sanjaya
2023-04-03 3:49 ` [PATCH bpf-next v4 1/2] docs/bpf: Add table to describe LRU properties Bagas Sanjaya
2023-04-03 22:14 ` Joe Stringer
2023-04-04 2:37 ` Bagas Sanjaya
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=ZCpK5wOI0ZEedhrr@debian.me \
--to=bagasdotme@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=joe@isovalent.com \
--cc=john.fastabend@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=martin.lau@linux.dev \
--cc=maxtram95@gmail.com \
--cc=oe-kbuild-all@lists.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).