From: Donghyeok Choe <d7271.choe@samsung.com>
To: John Ogness <john.ogness@linutronix.de>, pmladek@suse.com
Cc: linux-kernel@vger.kernel.org, takakura@valinux.co.jp,
youngmin.nam@samsung.com, hajun.sung@samsung.com,
seungh.jung@samsung.com, jh1012.choi@samsung.com
Subject: Re: printk: selective deactivation of feature ignoring non panic cpu's messages
Date: Tue, 4 Mar 2025 11:01:12 +0900 [thread overview]
Message-ID: <20250304020112.GA4025668@tiffany> (raw)
In-Reply-To: <8434fytakt.fsf@jogness.linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
On Fri, Feb 28, 2025 at 03:26:34PM +0106, John Ogness wrote:
> Perhaps Donghyeok might be happy enough if the debug option simply
> allowed the non-panic CPUs to store records. There are plenty of tools
> available to get at the dmesg buffer.
That's right. Just the addition of debug options can make me very happy.
If I find any problems using debug option on, I'll share them with you
immediately.
First, Shall we reflect only the patch that adds our debug option?
I will also study the problems raised. I want to be able to
participate in your discussion someday.
Thank you.
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2025-03-04 2:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250226031756epcas2p3674cccc82687effb40575aa5fa2956e0@epcas2p3.samsung.com>
2025-02-26 3:16 ` printk: selective deactivation of feature ignoring non panic cpu's messages Donghyeok Choe
2025-02-26 4:25 ` John Ogness
2025-02-26 13:58 ` Petr Mladek
2025-02-28 14:20 ` John Ogness
2025-03-04 2:01 ` Donghyeok Choe [this message]
2025-03-04 13:22 ` Petr Mladek
2025-03-04 13:59 ` John Ogness
2025-03-04 14:15 ` Petr Mladek
2025-03-17 5:06 ` Donghyeok Choe
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=20250304020112.GA4025668@tiffany \
--to=d7271.choe@samsung.com \
--cc=hajun.sung@samsung.com \
--cc=jh1012.choi@samsung.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=seungh.jung@samsung.com \
--cc=takakura@valinux.co.jp \
--cc=youngmin.nam@samsung.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 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.