mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tools/lib/lockdep: drop liblockdep
Date: Sat, 13 Nov 2021 08:37:59 -0500	[thread overview]
Message-ID: <YY+/t75dqrkDA9CM@sashalap> (raw)
In-Reply-To: <CAHk-=wiAWDZRzzG8T7fiBBESM9S-Uzy7OFVY9iv-UwjpAbhp-Q@mail.gmail.com>

On Fri, Nov 12, 2021 at 11:16:14AM -0800, Linus Torvalds wrote:
>On Fri, Nov 12, 2021 at 7:16 AM Sasha Levin <sashal@kernel.org> wrote:
>>
>> TL;DR: While a tool like liblockdep is useful, it probably doesn't
>> belong within the kernel tree.
>
>I have eagerly applied this patch, because I wasn't too happy with
>that thing in the first place.

Thank you for providing the room for this experiment nonetheless.

>However - I do note that there's signs of liblockdep in the
>tools/include/ directory still.
>
>Some of those headers may now be dead, and should be removed, but I
>didn't end up trying to figure it out, so I left them alone.
>
>This stupid shell command
>
>    git grep -il liblockdep tools/include/ |
>        sed 's:tools/include/::' |
>        while read i; do echo; echo $i:; echo; git grep $i tools/ ; done
>
>seems to say that yes, the <linux/module.h> header in the tools
>directory is still used, but the rest of them seem to only reference
>other dead headers.
>
>Hmm? It would be lovely to clean those headers up too and get rid of
>them - because those headers are very much part of why I hated the
>whole liblockdep mess, and why I was so happy to immediately apply
>this patch..

Yup, there are remenants in the common header directory which need more
careful auditing before removing. I'll send a follow-up patch during one
of the early -rc cycles.

Thanks!

-- 
Thanks,
Sasha

  reply	other threads:[~2021-11-13 13:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12 15:16 Sasha Levin
2021-11-12 19:16 ` Linus Torvalds
2021-11-13 13:37   ` Sasha Levin [this message]
2021-11-18  0:32 ` Paul Wise
2022-01-08 10:05   ` Paul Wise

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=YY+/t75dqrkDA9CM@sashalap \
    --to=sashal@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®