All of lore.kernel.org
 help / color / mirror / Atom feed
From: alexander.levin@verizon.com
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Ingo Molnar <mingo@redhat.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Future of liblockdep
Date: Thu, 4 May 2017 03:42:47 +0000	[thread overview]
Message-ID: <20170504034244.2zsukhays2txmz6w@sasha-lappy> (raw)
In-Reply-To: <1493846395.2564.42.camel@decadent.org.uk>

On Wed, May 03, 2017 at 10:19:55PM +0100, Ben Hutchings wrote:
> 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.  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.
> > 
> > Hi Ben,
> > 
> > I indeed received those patches and forwarded them on:
> > 
> > 	https://lkml.org/lkml/2016/6/17/1044
> > 
> > As well as an updated maintainers entry:
> > 
> > 	https://lkml.org/lkml/2016/7/29/431
> > 
> > But I failed to follow up on that and it seems to have fallen through the
> > cracks.
> > 
> > I'll get it back into shape, sorry.
> > 
> > I also don't expect many changes to liblockdep other than keeping it buildable,
> > if there are any missing features or bugs you'd like to discuss I'd be happy 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/lockdep-fix-oot-build.patch/
> https://sources.debian.net/src/linux/4.9.25-1/debian/patches/bugfix/all/lockdep-fix-soname.patch/
> https://sources.debian.net/src/linux/4.9.25-1/debian/patches/bugfix/all/tools-lib-lockdep-use-ldflags.patch/

Thanks Ben. I got it building again on 4.11, will run a few more tests in the
morning and will send a pull request.


-- 

Thanks,
Sasha

      reply	other threads:[~2017-05-04  3:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03 20:13 Future of liblockdep Ben Hutchings
2017-05-03 21:00 ` alexander.levin
2017-05-03 21:19   ` Ben Hutchings
2017-05-04  3:42     ` alexander.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=20170504034244.2zsukhays2txmz6w@sasha-lappy \
    --to=alexander.levin@verizon.com \
    --cc=ben@decadent.org.uk \
    --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 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.