From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Sasha Levin <sasha.levin@oracle.com>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 7/9] liblockdep: Support using LD_PRELOAD
Date: Fri, 10 May 2013 13:23:12 +0200 [thread overview]
Message-ID: <20130510112312.GA19356@gmail.com> (raw)
In-Reply-To: <20130510111719.GG31235@dyad.programming.kicks-ass.net>
* Peter Zijlstra <peterz@infradead.org> wrote:
> Would something like the below cure things? Obviously this hasn't been
> near a compiler for the entire thing still isn't wanting to compile for
> me.
this oneliner command should work it around for you on Quilt:
touch tools/lib/lockdep/uinclude/asm/hweight.h tools/lib/lockdep/uinclude/asm/sections.h tools/lib/lockdep/uinclude/linux/bitops.h tools/lib/lockdep/uinclude/linux/delay.h tools/lib/lockdep/uinclude/linux/ftrace.h tools/lib/lockdep/uinclude/linux/gfp.h tools/lib/lockdep/uinclude/linux/interrupt.h tools/lib/lockdep/uinclude/linux/linkage.h tools/lib/lockdep/uinclude/linux/mm_types.h tools/lib/lockdep/uinclude/linux/mutex.h tools/lib/lockdep/uinclude/linux/proc_fs.h tools/lib/lockdep/uinclude/linux/seq_file.h tools/lib/lockdep/uinclude/linux/system.h tools/lib/lockdep/uinclude/linux/util.h tools/lib/lockdep/uinclude/trace/events/lock.h
Thanks,
Ingo
next prev parent reply other threads:[~2013-05-10 11:23 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 15:58 [PATCH v3 0/9] liblockdep: userspace lockdep Sasha Levin
2013-05-09 15:58 ` [PATCH v3 1/9] lockdep: Be nice about building from userspace Sasha Levin
2013-05-09 15:58 ` [PATCH v3 2/9] liblockdep: Wrap kernel/lockdep.c to allow usage " Sasha Levin
2013-05-10 9:18 ` Peter Zijlstra
2013-05-10 9:38 ` Ingo Molnar
2013-05-10 10:11 ` Peter Zijlstra
2013-05-10 13:23 ` Sasha Levin
2013-05-10 14:03 ` Peter Zijlstra
2013-05-10 14:11 ` Sasha Levin
2013-05-10 14:12 ` Peter Zijlstra
2013-05-10 14:19 ` Peter Zijlstra
2013-05-10 14:23 ` Sasha Levin
2013-05-10 13:58 ` Peter Zijlstra
2013-05-09 15:58 ` [PATCH v3 3/9] liblockdep: Add public headers for pthread_mutex_t implementation Sasha Levin
2013-05-09 15:58 ` [PATCH v3 4/9] liblockdep: Add pthread_mutex_t test suite Sasha Levin
2013-05-09 15:58 ` [PATCH v3 5/9] liblockdep: Add public headers for pthread_rwlock_t implementation Sasha Levin
2013-05-09 15:58 ` [PATCH v3 6/9] liblockdep: Add pthread_rwlock_t test suite Sasha Levin
2013-05-09 15:58 ` [PATCH v3 7/9] liblockdep: Support using LD_PRELOAD Sasha Levin
2013-05-10 11:17 ` Peter Zijlstra
2013-05-10 11:23 ` Ingo Molnar [this message]
2013-05-10 11:46 ` Peter Zijlstra
2013-05-10 13:11 ` Peter Zijlstra
2013-05-10 13:57 ` Peter Zijlstra
2013-05-10 16:06 ` Sasha Levin
2013-05-10 16:21 ` Peter Zijlstra
2013-05-10 16:42 ` Sasha Levin
2013-05-09 15:58 ` [PATCH v3 8/9] liblockdep: Add the 'lockdep' user-space utility Sasha Levin
2013-05-10 9:19 ` Peter Zijlstra
2013-05-10 9:35 ` Ingo Molnar
2013-05-10 10:41 ` Peter Zijlstra
2013-05-10 11:00 ` Ingo Molnar
2013-05-10 11:10 ` Borislav Petkov
2013-05-10 11:07 ` Ingo Molnar
2013-05-09 15:58 ` [PATCH v3 9/9] liblockdep: Add a MAINTAINERS entry Sasha Levin
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=20130510112312.GA19356@gmail.com \
--to=mingo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sasha.levin@oracle.com \
--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