All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@linux.ibm.com>
Cc: Willy Tarreau <w@1wt.eu>,
	acme@redhat.com, linux-kernel@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH] tools headers: move the nolibc header from rcutorture to tools/include/nolibc/
Date: Sun, 30 Dec 2018 12:25:02 +0100	[thread overview]
Message-ID: <20181230112502.GA16126@gmail.com> (raw)
In-Reply-To: <20181229182508.GJ4170@linux.ibm.com>


* Paul E. McKenney <paulmck@linux.ibm.com> wrote:

> On Sat, Dec 29, 2018 at 07:04:53PM +0100, Willy Tarreau wrote:
> > As suggested by Ingo, this header file might benefit other tools than
> > just rcutorture. For now it's quite limited, but is easy to extend, so
> > exposing it into tools/include/nolibc/ will make it much easier to
> > adopt by other tools.
> > 
> > The mkinitrd.sh script in rcutorture was updated to use this new location.
> > 
> > Cc: Ingo Molnar <mingo@kernel.org>
> > Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> > Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> > Signed-off-by: Willy Tarreau <w@1wt.eu>
> 
> Thank you, Willy!  I have queued all four of these.  Should there
> be a MAINTAINERS file entry for the new include/nolibc home for this
> library code?

Very good idea - ack. Could we please also use the opportunity and move 
nolibc.h to a more prominent place, like in tools/include/nolibc/nolibc.h 
or so?

Thanks,

	Ingo

  parent reply	other threads:[~2018-12-30 11:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-29 18:04 [PATCH] tools headers: move the nolibc header from rcutorture to tools/include/nolibc/ Willy Tarreau
2018-12-29 18:25 ` Paul E. McKenney
2018-12-29 18:30   ` Willy Tarreau
2018-12-29 19:55     ` Paul E. McKenney
2018-12-29 20:00       ` Willy Tarreau
2018-12-30 11:25   ` Ingo Molnar [this message]
2018-12-30 11:38     ` Willy Tarreau
2018-12-30 11:50       ` Ingo Molnar

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=20181230112502.GA16126@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@infradead.org \
    --cc=acme@redhat.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.ibm.com \
    --cc=w@1wt.eu \
    /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.