From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
backports@vger.kernel.org
Cc: Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH 5/5] backports: add signature verification code
Date: Fri, 13 Oct 2017 11:38:34 +0200 [thread overview]
Message-ID: <1507887514.2551.40.camel@sipsolutions.net> (raw)
In-Reply-To: <2f943e21-1a4f-0863-dc7b-93640f9c4149@broadcom.com> (sfid-20171013_113631_961954_E067CB12)
On Fri, 2017-10-13 at 11:36 +0200, Arend van Spriel wrote:
> > add/remove: 246/0 grow/shrink: 1/0 up/down: 49050/0 (49050)
>
> Not sure what tool output this is so I assume it means 49k increase?
> That looks good I would say.
This was from scripts/bloat-o-meter (kernel sources). And yeah, that's
a hair under 48KiB :)
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2017-10-13 9:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 21:00 [PATCH 1/5] backports: move headers to be clearer Johannes Berg
2017-10-12 21:00 ` [PATCH 2/5] backports: add mktime64() Johannes Berg
2017-10-12 21:00 ` [PATCH 3/5] copy-list: move mpls includes Johannes Berg
2017-10-12 21:00 ` [PATCH 4/5] backports: add bin2hex() Johannes Berg
2017-10-13 8:55 ` Arend van Spriel
2017-10-13 8:56 ` Johannes Berg
2017-10-12 21:00 ` [PATCH 5/5] backports: add signature verification code Johannes Berg
2017-10-12 21:42 ` Johannes Berg
2017-10-12 22:05 ` Johannes Berg
2017-10-13 6:00 ` Johannes Berg
2017-10-13 9:02 ` Arend van Spriel
2017-10-13 9:09 ` Johannes Berg
2017-10-13 9:10 ` Johannes Berg
2017-10-13 9:36 ` Arend van Spriel
2017-10-13 9:38 ` Johannes Berg [this message]
2017-10-13 9:39 ` Johannes Berg
2017-10-13 10:22 ` Arend van Spriel
2017-10-13 10:23 ` Johannes Berg
2017-10-13 8:56 ` [PATCH 1/5] backports: move headers to be clearer Arend van Spriel
2017-10-13 8:57 ` Johannes Berg
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=1507887514.2551.40.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=johannes.berg@intel.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 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.