All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "Levin, Alexander (Sasha Levin)" <alexander.levin@verizon.com>
Cc: "acme@redhat.com" <acme@redhat.com>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Thomas Gleixner <tglx@linutronix.de>,
	"Paul E. McKenney" <paulmck@us.ibm.com>
Subject: Re: [PATCH 0/1] tools: liblockdep: move to using tools/include/
Date: Mon, 5 Jun 2017 09:31:34 +0200	[thread overview]
Message-ID: <20170605073134.gzkq3lez54o5wtkx@gmail.com> (raw)
In-Reply-To: <20170531003747.10557-1-alexander.levin@verizon.com>


* Levin, Alexander (Sasha Levin) <alexander.levin@verizon.com> wrote:

> This patch applies on top of the fixes sent a few days ago.
> 
> Just delete tools/lib/lockdep/uinclude and move the small bits of
> missing functionality (and a few empty headers) into
> tools/include/ .
> 
> Sasha Levin (1):
>   tools: liblockdep: remove private kernel headers
> 
>  tools/include/asm/sections.h                       |  0
>  tools/include/linux/compiler.h                     | 12 +++++
>  .../uinclude => include}/linux/debug_locks.h       |  1 +
>  tools/include/linux/delay.h                        |  0
>  tools/include/linux/ftrace.h                       |  0
>  tools/include/linux/gfp.h                          |  0

Ok, the new liblockdep code looks pretty clean and compact now - I've applied your 
earlier series plus this patch, will push out after a bit of testing.

There's one change I did: instead of the many zero size header files (which are 
hard to distinguish from empty files that tools like Quilt sometimes leave around) 
I've added explicit header guards to those otherwise empty files.

Thanks,

	Ingo

      parent reply	other threads:[~2017-06-05  7:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-31  0:38 [PATCH 0/1] tools: liblockdep: move to using tools/include/ Levin, Alexander (Sasha Levin)
2017-05-31  0:38 ` [PATCH 1/1] tools: liblockdep: remove private kernel headers Levin, Alexander (Sasha Levin)
2017-06-05  9:13   ` [tip:locking/core] tools/lib/lockdep: Remove " tip-bot for Levin, Alexander (Sasha Levin)
2017-06-05  7:31 ` Ingo Molnar [this message]

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=20170605073134.gzkq3lez54o5wtkx@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=alexander.levin@verizon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulmck@us.ibm.com \
    --cc=tglx@linutronix.de \
    /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.