From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752098AbdECVUU (ORCPT ); Wed, 3 May 2017 17:20:20 -0400 Received: from shadbolt.e.decadent.org.uk ([88.96.1.126]:58196 "EHLO shadbolt.e.decadent.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751216AbdECVUO (ORCPT ); Wed, 3 May 2017 17:20:14 -0400 Message-ID: <1493846395.2564.42.camel@decadent.org.uk> Subject: Re: Future of liblockdep From: Ben Hutchings To: alexander.levin@verizon.com Cc: Ingo Molnar , LKML Date: Wed, 03 May 2017 22:19:55 +0100 In-Reply-To: <20170503210032.q5ot4qximfdoqrk5@sasha-lappy> References: <1493842437.2564.40.camel@decadent.org.uk> <20170503210032.q5ot4qximfdoqrk5@sasha-lappy> Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-8xAIbaEeEkvR2FcJBKJb" X-Mailer: Evolution 3.22.6-1 Mime-Version: 1.0 X-SA-Exim-Connect-IP: 2a02:8011:400e:2:6f00:88c8:c921:d332 X-SA-Exim-Mail-From: ben@decadent.org.uk X-SA-Exim-Scanned: No (on shadbolt.decadent.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --=-8xAIbaEeEkvR2FcJBKJb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, 2017-05-03 at 21:00 +0000, alexander.levin@verizon.com wrote: > On Wed, May 03, 2017 at 09:13:57PM +0100, Ben Hutchings wrote: > > liblockdep hasn't been buildable since (I think) Linux 4.6.=C2=A0=C2=A0= I sent > > Sasha fixes for that last June and he included these in a pull request > > to Ingo, but somehow they never reached mainline.=C2=A0=C2=A0Linux 4.8 = broke > > liblockdep further, and I gave up packaging it for Debian. > >=20 > > There have been no other changes to liblockdep since then, other than a > > general change in the tools/ directory.=C2=A0=C2=A0Sasha's address in M= AINTAINERS > > is also out-of-date. > >=20 > > Please either maintain liblockdep properly or delete it.=C2=A0=C2=A0We = shouldn't > > keep code in the tree in a broken state. >=20 > Hi Ben, >=20 > I indeed received those patches and forwarded them on: >=20 > https://lkml.org/lkml/2016/6/17/1044 >=20 > As well as an updated maintainers entry: >=20 > https://lkml.org/lkml/2016/7/29/431 >=20 > But I failed to follow up on that and it seems to have fallen through the > cracks. >=20 > I'll get it back into shape, sorry. >=20 > I also don't expect many changes to liblockdep other than keeping it buil= dable, > if there are any missing features or bugs you'd like to discuss I'd be ha= ppy to > look into those. I had some other fixes that I was waiting to send: https://sources.debian.net/src/linux/4.9.25-1/debian/patches/bugfix/all/loc= kdep-fix-oot-build.patch/ https://sources.debian.net/src/linux/4.9.25-1/debian/patches/bugfix/all/loc= kdep-fix-soname.patch/ https://sources.debian.net/src/linux/4.9.25-1/debian/patches/bugfix/all/too= ls-lib-lockdep-use-ldflags.patch/ Ben. --=20 Ben Hutchings friends: People who know you well, but like you anyway. --=-8xAIbaEeEkvR2FcJBKJb Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAlkKSXsACgkQ57/I7JWG EQn1vhAAn3KpzAoHXVmfK54tOgpgdIsvp3yknA9SQ0lStYFgzAN3GBtCIwj99SZm G18iqTi3Uo/YziMAX0H/o7IQf5FYrdNuD0H+p4qlJDwdrvwmidgHsI+pXE2GSCAd aLOU+fTYByGW1aeRktBIAFtx4nsavlG8yVwo2lfPehKkmduhvQwdJArUWb/33B6p NkzEoiCOJG7fzi/4y5SDSKbOVo5OreEI+rwz0OxRZcGXKhpOafSBMki5XF57iRqQ oUroL6msIXM9s7iEGC4iC7JfYmWxfwSsWsDAb1K/V/su5W/3TVTmnOMkQDCFjKoZ eSBoyj5z/eKlV4oTm97hnad9PnFLm1B/jxhaldDf+7WTXzeILELwYphDJwdSHVLQ QitBbNpIPXYYmIIxfcwIvoAw+IkZcnB0jSh4jQKjPDL7xJt1nT+d0Vpu9Z9luSkU SxQYOyEInX8g2EPXS4TUtMnSFzo/rWfkRCuaYwnwXUP/w59ZX/bZy7WmywmJLw5H 0avxQqc4mReeYjSOfDb81TYogfNbrF7uZbybMltfq5jqNpUW5e06+jlE1DRyLP9D 5t/rZewB2yjA4sv+hs6mzI3C7Q1/V1D7PO0p5GlAhEA9Ss1A0BQYJ/VNdsEx+S1F dSav7pCCg9jZ3QrcZVJRRwaBi3W7WLIQhheVDlb44b+KeiE29hg= =U5m2 -----END PGP SIGNATURE----- --=-8xAIbaEeEkvR2FcJBKJb--