From: Ingo Molnar <mingo@kernel.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: mingo@redhat.com, "Ira W. Snyder" <iws@ovro.caltech.edu>,
linux-kernel@vger.kernel.org, peterz@infradead.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH 0/2] tools: lockdep: build fixes
Date: Tue, 4 Feb 2014 10:15:54 +0100 [thread overview]
Message-ID: <20140204091554.GC19156@gmail.com> (raw)
In-Reply-To: <52F05B7A.9040209@oracle.com>
* Sasha Levin <sasha.levin@oracle.com> wrote:
> On 01/31/2014 04:35 PM, Ira W. Snyder wrote:
> >From: "Ira W. Snyder" <iws@ovro.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@oracle.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
prev parent reply other threads:[~2014-02-04 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 21:35 [PATCH 0/2] tools: lockdep: build fixes Ira W. Snyder
2014-01-31 21:35 ` [PATCH 1/2] tools: lockdep: fix include of asm/hash.h Ira W. Snyder
2014-01-31 21:35 ` [PATCH 2/2] tools: lockdep: add include directory to allow tests to compile Ira W. Snyder
2014-02-04 3:16 ` [PATCH 0/2] tools: lockdep: build fixes Sasha Levin
2014-02-04 9:15 ` 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=20140204091554.GC19156@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=iws@ovro.caltech.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sasha.levin@oracle.com \
/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.