From: Linus Torvalds <torvalds@linuxfoundation.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Florian Weimer <fweimer@redhat.com>,
Nathan Chancellor <nathan@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
llvm@lists.linux.dev, linux-toolchains@vger.kernel.org
Subject: Re: [GIT PULL v2] Kbuild updates for v5.15-rc1
Date: Mon, 6 Sep 2021 09:30:01 -0700 [thread overview]
Message-ID: <CAHk-=wj=WpWO_V86cZH99LgZGBbvdDb4wR26ce5van0hJqjzLA@mail.gmail.com> (raw)
In-Reply-To: <20210906154642.GV1583@gate.crashing.org>
On Mon, Sep 6, 2021 at 8:50 AM Segher Boessenkool
<segher@kernel.crashing.org> wrote:
>
>
> Yes they are. It is the single standard way to get the functionality
> you want.
Sorry, but 'standard' is the part that the kernel simply doesn't do.
Just face it. The kernel isn't written with all those standards that
are designed for entirely different things in mind.
> I don't know why you think you can separate that. Take <stdarg.h> --
> there is no other (portable, standard) way to implement receiving
> variadic arguments.
You clearly haven't actually read the thread.
That was my whole argument. For the _historical_ situation.
Linus
next prev parent reply other threads:[~2021-09-06 16:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 23:30 [GIT PULL v2] Kbuild updates for v5.15-rc1 Masahiro Yamada
2021-09-03 22:53 ` Linus Torvalds
2021-09-03 23:04 ` Nathan Chancellor
2021-09-04 8:01 ` Florian Weimer
2021-09-04 13:19 ` Segher Boessenkool
2021-09-04 15:19 ` Florian Weimer
2021-09-04 16:19 ` Segher Boessenkool
2021-09-04 17:22 ` Linus Torvalds
2021-09-04 19:15 ` Segher Boessenkool
2021-09-04 19:58 ` Linus Torvalds
2021-09-06 15:46 ` Segher Boessenkool
2021-09-06 16:30 ` Linus Torvalds [this message]
2021-09-06 17:27 ` Segher Boessenkool
2021-09-06 18:11 ` Linus Torvalds
2021-09-06 18:27 ` Florian Weimer
2021-09-06 19:48 ` Segher Boessenkool
2021-09-06 20:14 ` Jakub Jelinek
2021-09-06 21:08 ` Linus Torvalds
2021-09-06 21:24 ` Linus Torvalds
2021-09-07 14:41 ` Segher Boessenkool
2021-09-06 21:52 ` Jakub Jelinek
2021-09-06 22:24 ` Linus Torvalds
2021-09-07 15:26 ` Segher Boessenkool
2021-09-07 14:52 ` Segher Boessenkool
2021-09-09 5:14 ` Masahiro Yamada
2021-09-07 14:29 ` Segher Boessenkool
2021-09-06 6:54 ` Florian Weimer
2021-09-06 16:02 ` Alexey Dobriyan
2021-09-08 3:09 ` Masahiro Yamada
2021-09-03 23:12 ` 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-=wj=WpWO_V86cZH99LgZGBbvdDb4wR26ce5van0hJqjzLA@mail.gmail.com' \
--to=torvalds@linuxfoundation.org \
--cc=clang-built-linux@googlegroups.com \
--cc=fweimer@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=segher@kernel.crashing.org \
/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;
as well as URLs for NNTP newsgroup(s).