All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: mingo@redhat.com, peterz@infradead.org, paulus@samba.org,
	acme@ghostprotocols.net, penberg@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/7] liblockdep: wrap kernel/lockdep.c to allow usage from userspace
Date: Sun, 3 Feb 2013 12:04:10 +0100	[thread overview]
Message-ID: <20130203110410.GA11739@gmail.com> (raw)
In-Reply-To: <1359737231-26127-1-git-send-email-sasha.levin@oracle.com>


So I applied your patches and did:

  cd tools/lib/lockdep
  make

and got:

comet:~/tip/tools/lib/lockdep> make
  CC FPIC            common.o
In file included from ./uinclude/linux/lockdep.h:13:0,
                 from 
/fast/mingo/tip/tools/lib/lockdep/common.c:4:
./../../../include/linux/lockdep.h:21:27: fatal error: linux/linkage.h: No such file or directory
compilation terminated.
make: *** [common.o] Error 1

Thanks,

	Ingo

  parent reply	other threads:[~2013-02-03 11:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 16:47 [PATCH v2 1/7] liblockdep: wrap kernel/lockdep.c to allow usage from userspace Sasha Levin
2013-02-01 16:47 ` [PATCH v2 2/7] liblockdep: public headers for mutex implementation Sasha Levin
2013-02-01 16:47 ` [PATCH v2 3/7] liblockdep: mutex test suite Sasha Levin
2013-02-01 16:47 ` [PATCH v2 4/7] liblockdep: public headers for rwlock implementation Sasha Levin
2013-02-01 16:47 ` [PATCH v2 5/7] liblockdep: rwlock test suite Sasha Levin
2013-02-01 16:47 ` [PATCH v2 6/7] liblockdep: add a MAINTAINERS entry Sasha Levin
2013-02-01 16:47 ` [PATCH v2 7/7] perf: integrate liblockdep support into perf Sasha Levin
2013-02-03 11:04 ` Ingo Molnar [this message]
2013-02-03 16:19   ` [PATCH v2 1/7] liblockdep: wrap kernel/lockdep.c to allow usage from userspace Sasha Levin
2013-02-03 19:10     ` 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=20130203110410.GA11739@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@ghostprotocols.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=penberg@kernel.org \
    --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.