From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Dan <dan.carpenter@oracle.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [RFC PATCH] kbuild: Add an option to enable -O1 and speed-up compilation time
Date: Mon, 23 May 2022 22:44:48 +0200 [thread overview]
Message-ID: <002f1094-3232-75c0-44e8-1ea77749cc2e@wanadoo.fr> (raw)
In-Reply-To: <CANiq72=GZs5CmAMGAMaHrp1yJ8b7nv3HrsWNeQ42kfy0z5uuAg@mail.gmail.com>
Le 23/05/2022 à 22:25, Miguel Ojeda a écrit :
> Hi Christophe,
>
> On Mon, May 23, 2022 at 9:11 AM Christophe JAILLET
> <christophe.jaillet@wanadoo.fr> wrote:
>>
>> +KBUILD_RUSTFLAGS_OPT_LEVEL_MAP := 1
>
> The patch seems based on linux-next -- is this intended? Thanks!
Yes, I work on -next.
Honestly, this "RUST flag" was just a mimic of the KBUILD_CFLAGS.
No real opinion on it, I just put something that looked consistent for a
patch that was only a RFC.
CJ
>
> Cheers,
> Miguel
>
next prev parent reply other threads:[~2022-05-23 20:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 9:04 Christophe JAILLET
2022-05-21 15:38 ` Masahiro Yamada
2022-05-23 12:34 ` Changbin Du
2022-05-23 12:50 ` Arnd Bergmann
2022-05-23 18:26 ` Nick Desaulniers
2022-05-23 20:16 ` Christophe JAILLET
2022-05-23 20:31 ` Nick Desaulniers
2022-05-24 14:16 ` Miguel Ojeda
2022-05-23 20:25 ` Miguel Ojeda
2022-05-23 20:44 ` Christophe JAILLET [this message]
2022-05-24 14:16 ` Miguel Ojeda
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=002f1094-3232-75c0-44e8-1ea77749cc2e@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ndesaulniers@google.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®