From: Ben Hutchings <ben@decadent.org.uk>
To: Sasha Levin <alexander.levin@verizon.com>,
Ingo Molnar <mingo@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Future of liblockdep
Date: Wed, 03 May 2017 21:13:57 +0100 [thread overview]
Message-ID: <1493842437.2564.40.camel@decadent.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 644 bytes --]
liblockdep hasn't been buildable since (I think) Linux 4.6. I sent
Sasha fixes for that last June and he included these in a pull request
to Ingo, but somehow they never reached mainline. Linux 4.8 broke
liblockdep further, and I gave up packaging it for Debian.
There have been no other changes to liblockdep since then, other than a
general change in the tools/ directory. Sasha's address in MAINTAINERS
is also out-of-date.
Please either maintain liblockdep properly or delete it. We shouldn't
keep code in the tree in a broken state.
Ben.
--
Ben Hutchings
friends: People who know you well, but like you anyway.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2017-05-03 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 20:13 Ben Hutchings [this message]
2017-05-03 21:00 ` Future of liblockdep alexander.levin
2017-05-03 21:19 ` Ben Hutchings
2017-05-04 3:42 ` alexander.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=1493842437.2564.40.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=alexander.levin@verizon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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