From: Matteo Croce <mcroce@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Matt Mackall <mpm@selenic.com>, Maninder Singh <maninder1.s@samsung.com>
Subject: Re: [PATCH] bloat-o-meter: fix typo in help
Date: Thu, 8 Mar 2018 00:39:26 +0100 [thread overview]
Message-ID: <CAGnkfhx-1AsoaJcZ9JYrSsQgMAWjznGTWGmSPs9fEjVe3+SOLQ@mail.gmail.com> (raw)
In-Reply-To: <20180214174718.4445-1-mcroce@redhat.com>
On Wed, Feb 14, 2018 at 6:47 PM, Matteo Croce <mcroce@redhat.com> wrote:
> the bloat-o-meter script has two typos in the help, fix both.
>
> Fixes: 192efb7a1f9b ("bloat-o-meter: provide 3 different arguments for data, function and All")
> Signed-off-by: Matteo Croce <mcroce@redhat.com>
> ---
> scripts/bloat-o-meter | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/bloat-o-meter b/scripts/bloat-o-meter
> index 94b664817ad9..d84a5674e95e 100755
> --- a/scripts/bloat-o-meter
> +++ b/scripts/bloat-o-meter
> @@ -15,7 +15,7 @@ signal(SIGPIPE, SIG_DFL)
> if len(sys.argv) < 3:
> sys.stderr.write("usage: %s [option] file1 file2\n" % sys.argv[0])
> sys.stderr.write("The options are:\n")
> - sys.stderr.write("-c cateogrize output based on symbole type\n")
> + sys.stderr.write("-c categorize output based on symbol type\n")
> sys.stderr.write("-d Show delta of Data Section\n")
> sys.stderr.write("-t Show delta of text Section\n")
> sys.exit(-1)
> --
> 2.14.3
>
Ping, anyone willing to review and eventually merge it?
Regards,
--
Matteo Croce
per aspera ad upstream
next prev parent reply other threads:[~2018-03-07 23:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 17:47 [PATCH] bloat-o-meter: fix typo in help Matteo Croce
2018-03-07 23:39 ` Matteo Croce [this message]
2018-03-08 1:51 ` Randy Dunlap
2018-03-08 4:26 ` Masahiro Yamada
2018-03-08 16:12 ` Masahiro Yamada
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=CAGnkfhx-1AsoaJcZ9JYrSsQgMAWjznGTWGmSPs9fEjVe3+SOLQ@mail.gmail.com \
--to=mcroce@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maninder1.s@samsung.com \
--cc=mpm@selenic.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 read-only IMAP folder(s) and NNTP newsgroup(s).