From: Borislav Petkov <bp@alien8.de>
To: Zhenzhong Duan <zhenzhong.duan@gmail.com>
Cc: Arvind Sankar <nivedita@alum.mit.edu>,
linux-kernel@vger.kernel.org, x86@kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Chao Fan <fanc.fnst@cn.fujitsu.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH v2] x86/boot/KASLR: Fix unused variable warning
Date: Fri, 10 Jan 2020 10:00:32 +0100 [thread overview]
Message-ID: <20200110090032.GB19453@zn.tnic> (raw)
In-Reply-To: <CAFH1YnNA9qfM4tPzKKDaQD6DPxnE=tJsB7AUZQBohDTW3zm=Xg@mail.gmail.com>
On Fri, Jan 10, 2020 at 10:27:02AM +0800, Zhenzhong Duan wrote:
> Yes. Will you send this formally?
And then a flood of fix-this-trivial-warning patches ensues?
You should know that they have the lowest prio when it comes to looking
at them.
> Not clear if there is other reason making KBUILD_CFLAGS for
> arch/x86/boot/compressed different from other part.
Maybe because the kernel proper build system should not break the
compressed kernel's build as the two are quite different... maybe for
historical raisins...
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-01-10 9:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 3:39 [PATCH v2] x86/boot/KASLR: Fix unused variable warning Zhenzhong Duan
2020-01-09 18:40 ` Borislav Petkov
2020-01-09 20:46 ` Arvind Sankar
2020-01-09 20:50 ` Borislav Petkov
2020-01-10 2:09 ` Zhenzhong Duan
2020-01-10 8:27 ` Borislav Petkov
2020-01-10 8:36 ` Zhenzhong Duan
2020-01-10 9:01 ` Borislav Petkov
2020-01-10 2:27 ` Zhenzhong Duan
2020-01-10 9:00 ` Borislav Petkov [this message]
2020-01-13 2:43 ` Zhenzhong Duan
2020-01-24 11:09 ` Borislav Petkov
2020-01-09 21:00 ` Thomas Gleixner
2020-01-10 8:46 ` Zhenzhong Duan
2020-01-10 13:13 ` Thomas Gleixner
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=20200110090032.GB19453@zn.tnic \
--to=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fanc.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nivedita@alum.mit.edu \
--cc=rafael.j.wysocki@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=zhenzhong.duan@gmail.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.