From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
"David S. Miller" <davem@davemloft.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: [GIT PULL] Crypto Fixes for 5.6
Date: Sat, 21 Mar 2020 08:43:23 -0700 [thread overview]
Message-ID: <CAHk-=wjGaHhVKyxBYCcw41j84ic1GbyAuGfN7nA9zCJyHZTw2Q@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pME41uHvhu5f_JGZbUNCuG0YVgRkBUQF9wtTO6YnMijw@mail.gmail.com>
On Fri, Mar 20, 2020 at 4:54 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> Funny, I always thought it was like that "for a good reason" that I
> just didn't know about -- assumedly something having to do with a
> difference between config time and compile time.
No, there _is_ a "good reason", but it is simply "hysterical raisins".
All scripting used to be done in Makefiles, for the simple reason that
GNU make supported all those shell escapes. The Kconfig language did
not.
The whole "shell escape in Kconfig" is relatively recent, and so we
still have old code (and people) used to the build-time makefile rules
rather than those newfangled Kconfig things.
Of course "relatively recent" is about two years by now. It's not like
we did it yesterday.
Anyway, your conversion patches look fine to me. I'm obviously not
taking them for 5.6, but if they go into -next and get some testing,
I'd love to have that cleanup in 5.7.
Linus
next prev parent reply other threads:[~2020-03-21 15:43 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 8:49 [GIT PULL] Crypto Update for 5.4 Herbert Xu
2019-09-18 19:55 ` pr-tracker-bot
2019-09-23 5:05 ` [GIT PULL] Crypto Fixes " Herbert Xu
2019-09-23 16:50 ` pr-tracker-bot
2019-10-10 12:38 ` Herbert Xu
2019-10-10 15:45 ` pr-tracker-bot
2019-11-17 1:00 ` Herbert Xu
2019-11-17 2:35 ` pr-tracker-bot
2019-12-02 6:20 ` [GIT PULL] Crypto Fixes for 5.5 Herbert Xu
2019-12-03 1:30 ` pr-tracker-bot
2019-12-14 8:47 ` Herbert Xu
2019-12-14 22:05 ` pr-tracker-bot
2020-01-15 15:08 ` Herbert Xu
2020-01-15 19:35 ` pr-tracker-bot
2020-02-13 3:32 ` [GIT PULL] Crypto Fixes for 5.6 Herbert Xu
2020-02-13 22:40 ` pr-tracker-bot
2020-02-24 6:00 ` Herbert Xu
2020-02-24 20:25 ` pr-tracker-bot
2020-03-12 11:57 ` Herbert Xu
2020-03-12 16:40 ` Linus Torvalds
2020-03-13 5:27 ` Masahiro Yamada
2020-03-20 23:53 ` Jason A. Donenfeld
2020-03-21 15:43 ` Linus Torvalds [this message]
2020-03-22 20:38 ` Jason A. Donenfeld
2020-03-22 20:55 ` Stephen Rothwell
2020-03-21 0:49 ` [PATCH RFC 0/3] x86: probe for assembler capabilities in Kconfig Jason A. Donenfeld
2020-03-21 0:49 ` [PATCH RFC 1/3] x86: probe assembler instead of kconfig instead of makefile Jason A. Donenfeld
2020-03-21 0:49 ` [PATCH RFC 2/3] crypto: x86 - rework configuration based on Kconfig Jason A. Donenfeld
2020-03-21 0:49 ` [PATCH RFC 3/3] crypto: curve25519 - do not pollute dispatcher based on assembler Jason A. Donenfeld
2020-03-12 17:05 ` [GIT PULL] Crypto Fixes for 5.6 pr-tracker-bot
2020-03-23 22:54 ` Herbert Xu
2020-03-23 23:05 ` pr-tracker-bot
2020-04-08 6:15 ` [GIT PULL] Crypto Fixes for 5.7 Herbert Xu
2020-04-09 4:55 ` pr-tracker-bot
2020-04-29 5:54 ` Herbert Xu
2020-04-29 16:50 ` pr-tracker-bot
2020-05-06 5:10 ` Herbert Xu
2020-05-06 17:25 ` pr-tracker-bot
2020-06-11 4:05 ` [GIT PULL] Crypto Fixes for 5.8 Herbert Xu
2020-06-11 18:25 ` pr-tracker-bot
2020-06-21 8:23 ` Herbert Xu
2020-06-21 17:10 ` pr-tracker-bot
2020-06-29 2:16 ` Herbert Xu
2020-06-29 17:15 ` pr-tracker-bot
2020-08-14 13:18 ` [GIT PULL] Crypto Fixes for 5.9 Herbert Xu
2020-08-14 20:34 ` pr-tracker-bot
2019-11-25 3:45 ` [GIT PULL] Crypto Update for 5.5 Herbert Xu
2019-11-26 4:25 ` pr-tracker-bot
2020-01-28 5:03 ` [GIT PULL] Crypto Update for 5.6 Herbert Xu
2020-01-29 0:30 ` pr-tracker-bot
2020-04-01 4:27 ` [GIT PULL] Crypto Update for 5.7 Herbert Xu
2020-04-01 22:35 ` pr-tracker-bot
2020-06-01 2:45 ` [GIT PULL] Crypto Update for 5.8 Herbert Xu
2020-06-01 19:35 ` pr-tracker-bot
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='CAHk-=wjGaHhVKyxBYCcw41j84ic1GbyAuGfN7nA9zCJyHZTw2Q@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=Jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.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 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.