mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Wise <pabs3@bonedaddy.net>
To: Sasha Levin <sashal@kernel.org>, mingo@kernel.org
Cc: peterz@infradead.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tools/lib/lockdep: drop liblockdep
Date: Thu, 18 Nov 2021 08:32:03 +0800	[thread overview]
Message-ID: <b82c6441832477653dfc4c2556b81b29bc1c75fa.camel@bonedaddy.net> (raw)
In-Reply-To: <20211112151602.1378857-1-sashal@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 644 bytes --]

On Fri, 2021-11-12 at 10:16 -0500, Sasha Levin wrote:

> TL;DR: While a tool like liblockdep is useful, it probably doesn't
> belong within the kernel tree.
...
> liblockdep should continue living in an external tree, syncing with
> the kernel often, in a controllable way.

I read that liblockdep and the lockdep tool are moving out of the Linux
kernel tree, but couldn't find where they will be moving to. An LWN
commenter suggested I contact you to ask about this. Thoughts?

https://lwn.net/Articles/875135/
https://lwn.net/Articles/876262/
https://lwn.net/Articles/876291/

-- 
bye,
pabs

https://bonedaddy.net/pabs3/

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2021-11-18  0:40 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
2021-11-18  0:32 ` Paul Wise [this message]
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=b82c6441832477653dfc4c2556b81b29bc1c75fa.camel@bonedaddy.net \
    --to=pabs3@bonedaddy.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=sashal@kernel.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®