From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Yonghong Song <yhs@meta.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>, Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Mykola Lysenko <mykolal@fb.com>,
Shuah Khan <shuah@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 1/3] selftests/bpf: align kbuild messages to standard
Date: Wed, 18 Jan 2023 05:15:55 +0000 [thread overview]
Message-ID: <20230118051555.2ud7mrt4tk6q6322@t-8ch.de> (raw)
In-Reply-To: <bc5beea9-0613-640b-b0dd-e54221c2fc06@meta.com>
On Tue, Jan 17, 2023 at 09:02:20PM -0800, Yonghong Song wrote:
>
>
> On 1/17/23 7:52 PM, Thomas Weißschuh wrote:
> > The common layout for kbuild messages is as follows:
> >
> > - 2 spaces
> > - 7 or more characters for the action
> > - 1 space
> > - name of the file being built/generated
> >
> > The custom message formatting included an additional space in the action
> > part, which leads to misalignments with the rest of kbuild.
>
> Could you give an example to show the output before/after the patch, and
> how it leads to mis-alignment and why it is a problem?
Before:
LD .../linux/tools/bpf/resolve_btfids/resolve_btfids-in.o
LINK resolve_btfids
CHK kernel/kheaders_data.tar.xz
After:
LD .../linux/tools/bpf/resolve_btfids/resolve_btfids-in.o
LINK resolve_btfids
CHK kernel/kheaders_data.tar.xz
The line starting with "LINK" has the filename "resolve_btfids" one
space character more to the right than the other lines.
It's slightly confusing when scanning the build logs.
> > Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> > ---
> > tools/testing/selftests/bpf/Makefile | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tools/testing/selftests/bpf/Makefile b/tools/testing/selftests/bpf/Makefile
> > index c22c43bbee19..5190c19295d4 100644
> > --- a/tools/testing/selftests/bpf/Makefile
> > +++ b/tools/testing/selftests/bpf/Makefile
> > @@ -98,7 +98,7 @@ Q =
> > msg =
> > else
> > Q = @
> > -msg = @printf ' %-8s%s %s%s\n' "$(1)" "$(if $(2), [$(2)])" "$(notdir $(3))" "$(if $(4), $(4))";
> > +msg = @printf ' %-7s%s %s%s\n' "$(1)" "$(if $(2), [$(2)])" "$(notdir $(3))" "$(if $(4), $(4))";
> > MAKEFLAGS += --no-print-directory
> > submake_extras := feature_display=0
> > endif
> >
next prev parent reply other threads:[~2023-01-18 5:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 3:52 [PATCH 0/3] align custom kbuild messages to standard layout Thomas Weißschuh
2023-01-18 3:52 ` [PATCH 1/3] selftests/bpf: align kbuild messages to standard Thomas Weißschuh
2023-01-18 5:02 ` Yonghong Song
2023-01-18 5:15 ` Thomas Weißschuh [this message]
2023-01-18 6:59 ` Yonghong Song
2023-01-18 3:52 ` [PATCH 2/3] bpf: iterators: " Thomas Weißschuh
2023-01-18 3:52 ` [PATCH 3/3] tools/resolve_btfids: " Thomas Weißschuh
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=20230118051555.2ud7mrt4tk6q6322@t-8ch.de \
--to=linux@weissschuh.net \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=masahiroy@kernel.org \
--cc=mykolal@fb.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yhs@fb.com \
--cc=yhs@meta.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
all inboxes | Powered by JetHome®