From: Sasha Levin <sasha.levin@oracle.com>
To: Andi Kleen <ak@linux.intel.com>, Robin Hack <rhack@redhat.com>
Cc: Eunbong Song <eunb.song@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Re: tools/liblockdep: Build failure
Date: Tue, 01 Apr 2014 11:47:18 -0400 [thread overview]
Message-ID: <533ADF86.1080209@oracle.com> (raw)
In-Reply-To: <20140401153453.GK32556@tassilo.jf.intel.com>
On 04/01/2014 11:34 AM, Andi Kleen wrote:
> On Tue, Apr 01, 2014 at 12:21:59PM +0200, Robin Hack wrote:
>> From: Robin Hack <rhack@redhat.com>
>> Copy asmlinkage macro to lockdep/uinclude/linux/linkage.h.
>
> You can just do
>
> #define asmlinkage
> #define __visible
Thanks Andi,
I've queued it up along with another fix for Ingo.
Thanks,
Sasha
prev parent reply other threads:[~2014-04-01 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 6:04 tools/liblockdep: Build failure Eunbong Song
2014-04-01 8:02 ` Robin Hack
2014-04-01 8:11 ` Robin Hack
2014-04-01 10:21 ` [PATCH] " Robin Hack
2014-04-01 10:34 ` Robin Hack
2014-04-01 15:34 ` Andi Kleen
2014-04-01 15:47 ` Sasha Levin [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=533ADF86.1080209@oracle.com \
--to=sasha.levin@oracle.com \
--cc=ak@linux.intel.com \
--cc=eunb.song@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rhack@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox