Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1635253 > unrolled thread
| Started by | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| First post | 2017-05-03 22:20 +0200 |
| Last post | 2017-05-04 05:50 +0200 |
| Articles | 4 — 2 participants |
Back to article view | Back to linux.kernel
Future of liblockdep Ben Hutchings <ben@decadent.org.uk> - 2017-05-03 22:20 +0200
Re: Future of liblockdep alexander.levin@verizon.com - 2017-05-03 23:10 +0200
Re: Future of liblockdep Ben Hutchings <ben@decadent.org.uk> - 2017-05-03 23:30 +0200
Re: Future of liblockdep alexander.levin@verizon.com - 2017-05-04 05:50 +0200
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Date | 2017-05-03 22:20 +0200 |
| Subject | Future of liblockdep |
| Message-ID | <tD8UF-1LK-1@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
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.
[toc] | [next] | [standalone]
| From | alexander.levin@verizon.com |
|---|---|
| Date | 2017-05-03 23:10 +0200 |
| Message-ID | <tD9H3-2kl-5@gated-at.bofh.it> |
| In reply to | #1635253 |
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. -- Thanks, Sasha
[toc] | [prev] | [next] | [standalone]
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Date | 2017-05-03 23:30 +0200 |
| Message-ID | <tDa0p-2s0-1@gated-at.bofh.it> |
| In reply to | #1635281 |
[Multipart message — attachments visible in raw view] — view raw
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/ Ben. -- Ben Hutchings friends: People who know you well, but like you anyway.
[toc] | [prev] | [next] | [standalone]
| From | alexander.levin@verizon.com |
|---|---|
| Date | 2017-05-04 05:50 +0200 |
| Message-ID | <tDfWa-6lQ-1@gated-at.bofh.it> |
| In reply to | #1635284 |
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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web