From: Linus Torvalds <[email protected]>
To: Willy Tarreau <[email protected]>
Cc: "Paul E. McKenney" <[email protected]>,
Linux Kernel Mailing List <[email protected]>,
Kernel Team <[email protected]>
Subject: Re: [GIT PULL] nolibc changes for v5.19
Date: Mon, 23 May 2022 14:13:20 -0700 [thread overview]
Message-ID: <CAHk-=wiFJKNPqLw1LW2pbfWxY50AGqBPJRMk2_KfpODD=-z5ng@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
On Mon, May 23, 2022 at 2:04 PM Willy Tarreau <[email protected]> wrote:
>
> On Mon, May 23, 2022 at 10:50:43PM +0200, Willy Tarreau wrote:
> > On Mon, May 23, 2022 at 01:30:37PM -0700, Linus Torvalds wrote:
> > >
> > > You speak the words, but you don't actually look at what it does.
> > >
> > > Try it.
> >
> > Why are you saying this ? I've figured the commands by trying
> > each of them.
Try this:
make tools/help
and then actually *LOOK* at what it prints out.
Notice how it says 'nolibc' is a target here.
And then think about it. Just for fun, try doing
make -C tools/ nolibc
make -C tools/ nolibc_install
like that help message implies you should do.
Does it work? No.
> work the same on all commands but actually:
>
> make -C tools/ nolibc_headers
Put another way: where did you find that "nolibc_headers"?
THAT is what I'm talking about. You are mentioning all these magical
things that don't match the documentation you yourself added.
Linus
next prev parent reply other threads:[~2022-05-23 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 18:24 [GIT PULL] nolibc changes for v5.19 Paul E. McKenney
2022-05-23 18:42 ` Linus Torvalds
2022-05-23 19:56 ` Willy Tarreau
2022-05-23 20:23 ` Willy Tarreau
2022-05-23 20:30 ` Linus Torvalds
2022-05-23 20:50 ` Willy Tarreau
2022-05-23 21:04 ` Willy Tarreau
2022-05-23 21:13 ` Linus Torvalds [this message]
2022-05-23 22:01 ` Willy Tarreau
2022-05-23 19:20 ` 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-=wiFJKNPqLw1LW2pbfWxY50AGqBPJRMk2_KfpODD=-z5ng@mail.gmail.com' \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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