From: Steven Rostedt <rostedt@goodmis.org>
To: Slavomir Kaslev <kaslevs@vmware.com>
Cc: linux-trace-devel@vger.kernel.org, slavomir.kaslev@gmail.com
Subject: Re: [PATCH 3/3] trace-cmd: Removed some unused #includes
Date: Thu, 14 Feb 2019 12:32:38 -0500 [thread overview]
Message-ID: <20190214123238.0acabfc6@gandalf.local.home> (raw)
In-Reply-To: <20190214140723.27804-3-kaslevs@vmware.com>
On Thu, 14 Feb 2019 16:07:23 +0200
Slavomir Kaslev <kaslevs@vmware.com> wrote:
> This patch removes several unused #include directives.
>
> No changes in behaviour intended.
>
> Signed-off-by: Slavomir Kaslev <kaslevs@vmware.com>
> ---
> lib/trace-cmd/trace-input.c | 9 ---------
> lib/trace-cmd/trace-recorder.c | 9 +--------
> 2 files changed, 1 insertion(+), 17 deletions(-)
>
> diff --git a/lib/trace-cmd/trace-input.c b/lib/trace-cmd/trace-input.c
> index b628570..34a8301 100644
> --- a/lib/trace-cmd/trace-input.c
> +++ b/lib/trace-cmd/trace-input.c
> @@ -4,22 +4,13 @@
> *
> */
> #define _LARGEFILE64_SOURCE
> -#include <dirent.h>
> #include <stdbool.h>
> #include <stdio.h>
> #include <stdlib.h>
> -#include <string.h>
> -#include <getopt.h>
> -#include <stdarg.h>
> -#include <sys/types.h>
> -#include <sys/stat.h>
> -#include <sys/wait.h>
> #include <sys/mman.h>
> -#include <pthread.h>
> #include <regex.h>
> #include <fcntl.h>
> #include <unistd.h>
> -#include <ctype.h>
> #include <errno.h>
>
> #include <linux/time64.h>
> diff --git a/lib/trace-cmd/trace-recorder.c b/lib/trace-cmd/trace-recorder.c
> index 1b6a995..0b8d98a 100644
> --- a/lib/trace-cmd/trace-recorder.c
> +++ b/lib/trace-cmd/trace-recorder.c
> @@ -4,18 +4,11 @@
> *
> */
> #define _LARGEFILE64_SOURCE
> -#include <dirent.h>
> #include <stdio.h>
> #include <stdlib.h>
> -#include <string.h>
> -#include <stdarg.h>
> -#include <sys/types.h>
> -#include <sys/stat.h>
> -#include <sys/wait.h>
> -#include <pthread.h>
> #include <fcntl.h>
> +#include <time.h>
> #include <unistd.h>
> -#include <ctype.h>
> #include <errno.h>
>
> #include "trace-cmd.h"
Nice cleanup.
Just an FYI, even on random patches, it's still good to have a cover
email for more than one patch series "[PATCH 0/3]", as it organizes it
better in inboxes.
BTW, I applied all of these.
Thanks Slavomir!
-- Steve
prev parent reply other threads:[~2019-02-14 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 14:07 [PATCH 1/3] trace-cmd: Fix tracecmd_recorder leaking file descriptors Slavomir Kaslev
2019-02-14 14:07 ` [PATCH 2/3] trace-cmd: Add defines for splice() flags on systems with old glibc Slavomir Kaslev
2019-02-14 14:07 ` [PATCH 3/3] trace-cmd: Removed some unused #includes Slavomir Kaslev
2019-02-14 17:32 ` Steven Rostedt [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=20190214123238.0acabfc6@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=kaslevs@vmware.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=slavomir.kaslev@gmail.com \
/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).