From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/2] bpf: Check truncation on 32bit div/mod by zero
Date: Tue, 27 Apr 2021 12:54:55 +0200 [thread overview]
Message-ID: <YIftf5pHE2iVmfGn@yuki> (raw)
In-Reply-To: <87k0oot5sg.fsf@suse.de>
Hi!
> bah, maybe we should just base64 encode doc strings in the JSON?
I do not think that this is a good idea, the main reason why I choose
JSON was because it is human readable...
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2021-04-27 10:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 12:01 [LTP] [PATCH 1/2] lapi/bpf: Add /= and %= Richard Palethorpe
2021-04-26 12:01 ` [LTP] [PATCH 2/2] bpf: Check truncation on 32bit div/mod by zero Richard Palethorpe
2021-04-27 9:30 ` Petr Vorel
2021-04-27 9:50 ` Richard Palethorpe
2021-04-27 10:54 ` Cyril Hrubis [this message]
2021-04-27 10:58 ` Cyril Hrubis
2021-04-27 12:03 ` Petr Vorel
2021-04-27 9:54 ` Cyril Hrubis
2021-04-27 11:25 ` Richard Palethorpe
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=YIftf5pHE2iVmfGn@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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