From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: [PATCH liburing] test/stdout: fix strcmp non-\0 string
Date: Tue, 16 Jun 2020 13:47:35 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <ec5c66bd2bf8ae8c190ebf4894f58a039c131845.1592336391.git.asml.silence@gmail.com>
On 6/16/20 1:42 PM, Pavel Begunkov wrote:
> After copying len(str) bytes of a string, the copy won't necessary have
> \0 terminator, that makes test_pipe_io_fixed() to fail. Use memcmp().
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2020-06-16 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 19:42 [PATCH liburing] test/stdout: fix strcmp non-\0 string Pavel Begunkov
2020-06-16 19:47 ` Jens Axboe [this message]
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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