From: Maxim Mikityanskiy <maxtram95@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: kernel test robot <lkp@intel.com>,
Joe Stringer <joe@isovalent.com>,
bpf@vger.kernel.org, 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,
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 11:49:54 +0300 [thread overview]
Message-ID: <ZCqTMq3sHMrx2boI@mail.gmail.com> (raw)
In-Reply-To: <ZCpK5wOI0ZEedhrr@debian.me>
On Mon, 03 Apr 2023 at 10:41:27 +0700, Bagas Sanjaya wrote:
> 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?
I have the same warning on Arch Linux.
$ dot --version
dot - graphviz version 7.1.0 (0)
next prev parent reply other threads:[~2023-04-03 8:50 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
2023-04-03 8:49 ` Maxim Mikityanskiy [this message]
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=ZCqTMq3sHMrx2boI@mail.gmail.com \
--to=maxtram95@gmail.com \
--cc=ast@kernel.org \
--cc=bagasdotme@gmail.com \
--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=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).