linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Denis Efremov <efremov@linux.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Michal Marek <michal.lkml@markovi.net>,
	Emil Velikov <emil.l.velikov@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] modpost: check for static EXPORT_SYMBOL* functions
Date: Thu, 1 Aug 2019 09:17:25 +0300	[thread overview]
Message-ID: <ad31b3a8-f662-ef14-148b-347f3671e7d3@linux.com> (raw)
In-Reply-To: <CAK7LNARrA7dKWaqqtbNUS2yOJfkign4CNvcn_bp2BLyvVAj2FQ@mail.gmail.com>

On 01.08.2019 05:20, Masahiro Yamada wrote:
> 
> The build time impact is very limited.
> I guess this measurement is unnecessary in the commit log.
> 

Thank you for your observations! It was not easy for me to guess to do
it this way because of my limited knowledge about kbuild && modpost
work. In v5 I've only updated commit log: measurements removed, "The
build time impact is very limited and is almost at the unnoticeable
level (< 1 sec)" added instead. Fell free to edit it if you want.

Denis

  reply	other threads:[~2019-08-01  6:17 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-14 15:28 [RFC PATCH] modpost: check for static EXPORT_SYMBOL* functions Denis Efremov
2019-07-15 14:43 ` Emil Velikov
2019-07-27 12:55 ` Masahiro Yamada
2019-07-27 19:13   ` Denis Efremov
2019-07-28  2:00     ` Masahiro Yamada
2019-07-28 10:09 ` [PATCH] " Denis Efremov
2019-07-29  3:29   ` Masahiro Yamada
2019-07-29  9:51     ` Denis Efremov
2019-07-29  5:13   ` Stephen Rothwell
2019-07-29  9:16     ` Denis Efremov
2019-07-29  9:32       ` Masahiro Yamada
2019-07-29 12:40       ` Stephen Rothwell
2019-07-29 12:52         ` Denis Efremov
2019-07-29 13:07           ` Stephen Rothwell
2019-07-29  9:22 ` [PATCH v2] " Denis Efremov
2019-07-29 12:20   ` Stephen Rothwell
2019-07-29 12:47     ` Denis Efremov
2019-07-29 14:18 ` [PATCH v3] " Denis Efremov
2019-07-29 22:26   ` Stephen Rothwell
2019-07-30  6:59     ` Denis Efremov
2019-07-30 16:29       ` Masahiro Yamada
2019-07-30 16:44         ` Denis Efremov
2019-07-30 17:21           ` Masahiro Yamada
2019-07-30 18:11 ` [PATCH v4] " Denis Efremov
2019-07-30 18:15   ` Denis Efremov
2019-07-31  8:54   ` Masahiro Yamada
2019-08-01  2:20     ` Masahiro Yamada
2019-08-01  6:17       ` Denis Efremov [this message]
2019-08-01  6:06 ` [PATCH v5] " Denis Efremov
2019-08-07 15:12   ` Masahiro Yamada
2019-08-13 16:07     ` Masahiro Yamada
2019-08-13 21:11       ` Denis Efremov

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=ad31b3a8-f662-ef14-148b-347f3671e7d3@linux.com \
    --to=efremov@linux.com \
    --cc=emil.l.velikov@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=sfr@canb.auug.org.au \
    --cc=yamada.masahiro@socionext.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).