From: Richard Palethorpe <rpalethorpe@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/add_key04: new test for associative array bug
Date: Mon, 20 Nov 2017 10:09:03 +0100 [thread overview]
Message-ID: <87shd9iafk.fsf@rpws.prws.suse.cz> (raw)
In-Reply-To: <20171108211123.94429-1-ebiggers3@gmail.com>
Hello,
This looks good to me, except for some nit picking: sprintf could be
snprintf and probably you only need one 'associative'. However I would
be happy for this to be merged as-is.
--
Thank you,
Richard.
prev parent reply other threads:[~2017-11-20 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 21:11 [LTP] [PATCH] syscalls/add_key04: new test for associative array bug Eric Biggers
2017-11-09 8:29 ` Richard Palethorpe
2017-11-20 9:09 ` Richard Palethorpe [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 \
--in-reply-to=87shd9iafk.fsf@rpws.prws.suse.cz \
--to=rpalethorpe@suse.de \
--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