[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140204091554.GC19156@gmail.com>
Date: Tue, 4 Feb 2014 10:15:54 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Sasha Levin <sasha.levin@...cle.com>
Cc: mingo@...hat.com, "Ira W. Snyder" <iws@...o.caltech.edu>,
linux-kernel@...r.kernel.org, peterz@...radead.org,
Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH 0/2] tools: lockdep: build fixes
* Sasha Levin <sasha.levin@...cle.com> wrote:
> On 01/31/2014 04:35 PM, Ira W. Snyder wrote:
> >From: "Ira W. Snyder" <iws@...o.caltech.edu>
> >
> >Included are some fixes to the tools/lib/lockdep source tree to fix some
> >build issues.
> >
> >Ira W. Snyder (2):
> > tools: lockdep: fix include of asm/hash.h
> > tools: lockdep: add include directory to allow tests to compile
> >
> > tools/lib/lockdep/Makefile | 2 +-
> > tools/lib/lockdep/uinclude/asm/hash.h | 6 ++++++
> > 2 files changed, 7 insertions(+), 1 deletion(-)
> > create mode 100644 tools/lib/lockdep/uinclude/asm/hash.h
> >
>
> Acked-by: Sasha Levin <sasha.levin@...cle.com>
>
> Ingo, How would you like the liblockdep things to work? Would you be
> picking them yourself directly to the locking tree or should I be
> sending a pull request?
Let's try a pull request? Initially it might need several iterations
(rebasing) as the requirements for pull requests are always much more
stringent, as I cannot fix up small details.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists