linux-kbuild.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rd.dunlab@gmail.com
To: linux-kbuild@vger.kernel.org
Cc: Randy Dunlap <rd.dunlab@gmail.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	rdunlap@infradead.org
Subject: [PATCH 4/4] scripts: namespace.pl: add blank section separator line
Date: Wed, 02 Oct 2019 20:13:16 -0700	[thread overview]
Message-ID: <20191003031312.433635881@gmail.com> (raw)
In-Reply-To: 20191003031312.157994411@gmail.com

[-- Attachment #1: scr-namespace-blank-sep-line.patch --]
[-- Type: text/plain, Size: 706 bytes --]

Most namespace report sections are separated by blank lines, but a
blank line is needed before the "multiply defined" output as a
separator, to make it easier to find the beginning of this section
of output.

Signed-off-by: Randy Dunlap <rd.dunlab@gmail.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Randy Dunlap <rdunlap@infradead.org>
---
patch 4/4:
 scripts/namespace.pl |    1 +
 1 file changed, 1 insertion(+)

--- linux-next-20191002.orig/scripts/namespace.pl
+++ linux-next-20191002/scripts/namespace.pl
@@ -368,6 +368,7 @@ sub drop_def
 
 sub list_multiply_defined
 {
+	printf "\n";
 	foreach my $name (keys(%def)) {
 		if ($#{$def{$name}} > 0) {
 			# Special case for cond_syscall

      parent reply	other threads:[~2019-10-03  3:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-03  3:13 [PATCH 0/4] scripts: update namespace.pl rd.dunlab
2019-10-03  3:13 ` [PATCH 1/4] scripts: namespace.pl: handle lib-ksyms.o as lib.a rd.dunlab
2019-10-23  5:22   ` Masahiro Yamada
2019-10-03  3:13 ` [PATCH 2/4] scripts: namespace.pl: add some x86 object files to nmexception rd.dunlab
2019-10-23  5:33   ` Masahiro Yamada
2019-10-03  3:13 ` [PATCH 3/4] scripts: namespace.pl: add .o to nmexception file names and fix "acpica" rd.dunlab
2019-10-23  5:34   ` Masahiro Yamada
2019-10-03  3:13 ` rd.dunlab [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=20191003031312.433635881@gmail.com \
    --to=rd.dunlab@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --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).