All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Waiman Long <longman@redhat.com>,
	Will Deacon <will@kernel.org>, Boqun Feng <boqun.feng@gmail.com>,
	Dmitry Vyukov <dvyukov@google.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] tomoyo update and hung task update for v6.2
Date: Sat, 14 Jan 2023 10:38:38 +0100	[thread overview]
Message-ID: <Y8J4HuZnzsuc8Ln1@gmail.com> (raw)
In-Reply-To: <a557d6e4-8354-f39b-32e1-b10e8a6fc04a@I-love.SAKURA.ne.jp>


* Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> wrote:

> On 2023/01/13 22:28, Linus Torvalds wrote:
> > On Tue, Jan 10, 2023 at 5:07 AM Tetsuo Handa
> > <penguin-kernel@i-love.sakura.ne.jp> wrote:
> >>
> >> A Makefile update for making it possible to remove scripts/bin2c program, and
> >> an improvement for making it easier to understand syzbot's hung task reports.
> > 
> > That hungtask change I'd _really_ like to get from the locking people,
> > not from a random - and completely unrelated tree.
> > 
> 
> OK. Then, please ignore this request.
> 
> Peter or Ingo, will you send
> "[PATCH v2 (repost)] locking/lockdep: add debug_show_all_lock_holders()" at
> https://lkml.kernel.org/r/41f43b27-d910-78e0-c0b3-f2885fe1cd22@I-love.SAKURA.ne.jp
> via your locking tree?

Thanks for the heads-up - this patch was still in my (overly long ...) 
holiday TODO list - I have replied to it now in the original thread.

[ Executive summary: I don't disagree with the functionality, but I think 
                     we can do this in a simpler/cleaner fashion. ]

Thanks,

	Ingo

      reply	other threads:[~2023-01-14  9:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10 11:07 [GIT PULL] tomoyo update and hung task update for v6.2 Tetsuo Handa
2023-01-13 13:28 ` Linus Torvalds
2023-01-13 13:48   ` Tetsuo Handa
2023-01-14  9:38     ` Ingo Molnar [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=Y8J4HuZnzsuc8Ln1@gmail.com \
    --to=mingo@kernel.org \
    --cc=boqun.feng@gmail.com \
    --cc=dvyukov@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@redhat.com \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --cc=will@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 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.