From: Helen Koike <helen@koikeco.de>
To: "Leonardo Brás" <leobras.c@gmail.com>, lkcamp@lists.libreplanetbr.org
Cc: x86@kernel.org, linux-kbuild@vger.kernel.org,
Matthew Wilcox <willy6545@gmail.com>,
linux-kernel@vger.kernel.org,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Andy Lutomirski <luto@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Michal Marek <michal.lkml@markovi.net>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [Lkcamp] [PATCH 0/4] Adds -Wshadow=local on KBUILD_HOSTCFLAGS
Date: Wed, 17 Oct 2018 01:45:54 -0300 [thread overview]
Message-ID: <00beb3a2-e68d-4f6c-d69a-8413acc214c4@koikeco.de> (raw)
In-Reply-To: <20181017000722.GA20892@WindFlash>
Hi Leonardo,
Thanks for the patches.
On 10/16/18 9:07 PM, Leonardo Brás wrote:
> This patchset add -Wshadow=local on KBUILD_HOSTCFLAGS and fixes
> all code that show this warning.
>
> The third patch was already submitted, but was not merged yet.
> I like to think it's part of this patchset, but if it was
> already merged, please ignore it.
You can check if it was merged in the maintainers' tree, if it is not
there then it is not merged :)
imho, I would prefer if you submitted it as a v2 with an explanation of
what changed since v1 (e.g. new commits) or even stating that nothing
has changed and you just regrouped it.
Or better, you could also not re-submit it and just point out that this
series depends on a previous commit (with a link to it).
>
> Leonardo Brás (4):
> Adds -Wshadow=local on KBUILD_HOSTCFLAGS
> Renames variable to fix shadow warning.
> kbuild: Removes unnecessary shadowed local variable and optimize
> testing.
> Changes macro usage to avoid shadowing a variable.
>
> Makefile | 2 +-
> arch/x86/entry/vdso/vdso2c.h | 4 ++--
> scripts/asn1_compiler.c | 7 +++----
> scripts/mod/file2alias.c | 14 ++++++++------
> 4 files changed, 14 insertions(+), 13 deletions(-)
>
I hope this helps.
Regards,
Helen
prev parent reply other threads:[~2018-10-17 4:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 0:07 Leonardo Brás
2018-10-17 4:45 ` Helen Koike [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=00beb3a2-e68d-4f6c-d69a-8413acc214c4@koikeco.de \
--to=helen@koikeco.de \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=leobras.c@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcamp@lists.libreplanetbr.org \
--cc=luto@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=willy6545@gmail.com \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®