linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Kernel Team <kernel-team@fb.com>
Subject: Re: [GIT PULL] nolibc changes for v5.19
Date: Mon, 23 May 2022 23:04:43 +0200	[thread overview]
Message-ID: <20220523210443.GD25949@1wt.eu> (raw)
In-Reply-To: <20220523205043.GA25949@1wt.eu>

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:
> > On Mon, May 23, 2022 at 1:23 PM Willy Tarreau <w@1wt.eu> wrote:
> > >
> > > So I've figured it again. When you run:
> > >
> > >    make tools/help
> > >
> > > you get the help of tools/ commands, [..]
> > 
> > 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.

I think I found it:

   make -C tools/ <tool>_<command>

and:

   make tools/<tool>_<command>

work the same on all commands but actually:

   make -C tools/ nolibc_headers

fails while:

   make tools/nolibc_headers

works. I've essentially used the latter by simplicity without noticing
that it doesn't work as suggested with <tool>_install, and I guess
that's what you got.

I'll check why it's like this and will propose a fix.

Thanks,
Willy

  reply	other threads:[~2022-05-23 21:04 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 [this message]
2022-05-23 21:13             ` Linus Torvalds
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=20220523210443.GD25949@1wt.eu \
    --to=w@1wt.eu \
    --cc=kernel-team@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=torvalds@linux-foundation.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).