public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Stephen Boyd <sboyd@kernel.org>,
	Felix.Kuehling@amd.com, Qianli Zhao <zhaoqianligood@gmail.com>,
	akpm@linux-foundation.org, axboe@kernel.dk
Cc: john.stultz@linaro.org, ben.dooks@codethink.co.uk,
	bfields@redhat.com, cl@rock-chips.com,
	linux-kernel@vger.kernel.org, zhaoqianli@xiaomi.com
Subject: Re: [RFC V2] kthread: add object debug support
Date: Sun, 16 Aug 2020 21:38:26 +0200	[thread overview]
Message-ID: <87d03qjs99.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <159748064613.2270147.9288160745183605164@swboyd.mtv.corp.google.com>

On Sat, Aug 15 2020 at 01:37, Stephen Boyd wrote:
> Quoting Thomas Gleixner (2020-08-12 03:27:03)
>> or any other variant of insanity which makes the check claim that this
>> is statically initialized then you rightfully can keep the pieces :)
>
> Makes sense. Maybe this "technique" should be documented in
> Documentation/core-api/debug-objects.rst? I can cook up a patch to add
> is_static_object() to the Fixup functions section.

Sure. Better documentation is always a good thing.

Thanks,

        tglx

  reply	other threads:[~2020-08-16 19:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-12  5:14 [RFC V2] kthread: add object debug support Qianli Zhao
2020-08-12  8:34 ` Stephen Boyd
2020-08-12 10:27   ` Thomas Gleixner
2020-08-15  8:37     ` Stephen Boyd
2020-08-16 19:38       ` Thomas Gleixner [this message]
2020-08-12 10:10 ` Thomas Gleixner
2020-08-20  6:25 ` [kthread] 2e7d8748eb: last_state.is_incomplete_run kernel test robot
2020-08-27  3:49   ` qianli zhao
2020-09-02  7:53     ` Chen, Rong A

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=87d03qjs99.fsf@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=Felix.Kuehling@amd.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=ben.dooks@codethink.co.uk \
    --cc=bfields@redhat.com \
    --cc=cl@rock-chips.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sboyd@kernel.org \
    --cc=zhaoqianli@xiaomi.com \
    --cc=zhaoqianligood@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox