From: Bill O'Donnell <billodo@redhat.com>
To: Anand Jain <anand.jain@oracle.com>
Cc: fstests@vger.kernel.org, zlang@kernel.org
Subject: Re: [PATCH 0/4] fstest: fix compilation warnings
Date: Mon, 30 Jan 2023 14:11:43 -0600 [thread overview]
Message-ID: <Y9gkfwzV2qU1YWi7@redhat.com> (raw)
In-Reply-To: <cover.1674870429.git.anand.jain@oracle.com>
On Sun, Jan 29, 2023 at 10:42:29AM +0800, Anand Jain wrote:
> This patch set addresses several compilation warnings and is based on
> the for-next.
Good idea. The warnings have become pretty distracting. Thanks.
For the series...
Reviewed-by: Bill O'Donnell <bodonnel@redhat.com>
>
> Anand Jain (4):
> fstests: doio.c, fix missing initialization of -C arg
> fstests: fstest.c, fix compile warnings replace sprintf with snprintf
> fstests: t_getcwd.c, fix a warning related to buffer overflow
> fstests: aiodio_sparse2.c, fix compiler warning buffer overflow
>
> ltp/doio.c | 1 +
> src/aio-dio-regress/aiodio_sparse2.c | 1 +
> src/fstest.c | 17 +++++++++++++----
> src/t_getcwd.c | 4 ++--
> 4 files changed, 17 insertions(+), 6 deletions(-)
>
> --
> 2.38.1
>
prev parent reply other threads:[~2023-01-30 20:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 2:42 [PATCH 0/4] fstest: fix compilation warnings Anand Jain
2023-01-29 2:42 ` [PATCH 1/4] fstests: doio.c, fix missing initialization of -C arg Anand Jain
2023-01-29 2:42 ` [PATCH 2/4] fstests: fstest.c, fix compile warnings replace sprintf with snprintf Anand Jain
2023-01-29 2:42 ` [PATCH 3/4] fstests: t_getcwd.c, fix a warning related to buffer overflow Anand Jain
2023-01-29 2:42 ` [PATCH 4/4] fstests: aiodio_sparse2.c, fix compiler warning " Anand Jain
2023-01-30 20:11 ` Bill O'Donnell [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=Y9gkfwzV2qU1YWi7@redhat.com \
--to=billodo@redhat.com \
--cc=anand.jain@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=zlang@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.