From: Oleksandr Natalenko <oleksandr@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jessica Yu <jeyu@kernel.org>, Tejun Heo <tj@kernel.org>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Joel Fernandes <joel@joelfernandes.org>,
David Howells <dhowells@redhat.com>,
Patrick Bellasi <patrick.bellasi@arm.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
"Eric W . Biederman" <ebiederm@xmission.com>
Subject: [PATCH 0/1] init/Kconfig: enable -O3 for all arches
Date: Wed, 11 Dec 2019 11:46:18 +0100 [thread overview]
Message-ID: <20191211104619.114557-1-oleksandr@redhat.com> (raw)
The purpose of this submission is to expose -O3 for all the
architectures, not only ARC, since it helps in hunting some bugs (see
the commit message for specific example).
Previously this was posted as RFC here: [1]. With this submission I'm
addressing Krzysztof's concern regarding commit message. No other
changes are made.
The RFC was accepted into -mm tree here: [2]. If needed, please replace
that one with this one since this one has a nicer commit message.
The patch is made against next-20191210 tag.
Thanks.
[1] https://lore.kernel.org/lkml/20191210145657.105808-1-oleksandr@redhat.com/
[2] https://marc.info/?l=linux-mm-commits&m=157602335225239&w=2
Oleksandr Natalenko (1):
init/Kconfig: enable -O3 for all arches
init/Kconfig | 1 -
1 file changed, 1 deletion(-)
--
2.24.1
next reply other threads:[~2019-12-11 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 10:46 Oleksandr Natalenko [this message]
2019-12-11 10:46 ` [PATCH 1/1] " Oleksandr Natalenko
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=20191211104619.114557-1-oleksandr@redhat.com \
--to=oleksandr@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=jeyu@kernel.org \
--cc=joel@joelfernandes.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=patrick.bellasi@arm.com \
--cc=tj@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®