From: Ben Hutchings <ben@decadent.org.uk>
To: Sasha Levin <Alexander.Levin@microsoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Build fixes for liblockdep
Date: Wed, 29 Aug 2018 00:59:11 +0100 [thread overview]
Message-ID: <20180828235911.GL18030@decadent.org.uk> (raw)
In-Reply-To: <20180828235656.GH18030@decadent.org.uk>
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
Also, please update your address in MAINTAINERS.
Ben.
On Wed, Aug 29, 2018 at 12:56:56AM +0100, Ben Hutchings wrote:
> In addition to the patch I recently sent for lockdep itself, the
> following fixes are also needed to make liblockdep build.
>
> Ben.
>
> Bastian Blank (1):
> liblockdep: Stub NMI watchdog reset
>
> Ben Hutchings (1):
> liblockdep: Stub task_struct::state
>
> tools/include/linux/lockdep.h | 4 ++++
> tools/include/linux/nmi.h | 12 ++++++++++++
> 2 files changed, 16 insertions(+)
> create mode 100644 tools/include/linux/nmi.h
>
--
Ben Hutchings
For every complex problem
there is a solution that is simple, neat, and wrong.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2018-08-28 23:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 23:56 [PATCH 0/2] Build fixes for liblockdep Ben Hutchings
2018-08-28 23:57 ` [PATCH 1/2] liblockdep: Stub NMI watchdog reset Ben Hutchings
2018-08-28 23:57 ` [PATCH 2/2] liblockdep: Stub task_struct::state Ben Hutchings
2018-08-28 23:59 ` Ben Hutchings [this message]
2018-08-29 0:19 ` [PATCH 0/2] Build fixes for liblockdep Sasha Levin
-- strict thread matches above, loose matches on Subject: below --
2018-08-28 23:36 Ben Hutchings
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=20180828235911.GL18030@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=Alexander.Levin@microsoft.com \
--cc=linux-kernel@vger.kernel.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