From: Donghyeok Choe <d7271.choe@samsung.com>
To: Petr Mladek <pmladek@suse.com>
Cc: linux-kernel@vger.kernel.org, rostedt@goodmis.org,
john.ogness@linutronix.de, senozhatsky@chromium.org,
takakura@valinux.co.jp, youngmin.nam@samsung.com,
hajun.sung@samsung.com, seungh.jung@samsung.com,
jh1012.choi@samsung.com, d7271.choe@samsung.com
Subject: Re: [PATCH v2] printk/panic: Add option to allow non-panic CPUs to write to the ring buffer.
Date: Mon, 24 Mar 2025 11:16:54 +0900 [thread overview]
Message-ID: <20250324021654.GA15429@tiffany> (raw)
In-Reply-To: <Z9wz9Wk28lmvy4Dg@pathway.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
On Thu, Mar 20, 2025 at 04:27:49PM +0100, Petr Mladek wrote:
> Result:
>
> The patch has been comitted into printk/linux.git,
> branch for-6.15, see
> https://web.git.kernel.org/pub/scm/linux/kernel/git/printk/linux.git/commit/?h=for-6.15&id=c1aa3daa517292303d98ff61f0440c354669f948
>
> Feel free to ask me take it back. I am going to wait few days
> before sending pull request for 6.15.
Thank you for providing detailed explanations about your modifications.
I really appreciate the clarity, and I have learned a lot from your changes.
Your approach makes perfect sense, and I have no objections to
what you are planning to do.
Thank you.
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2025-03-24 2:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250318022458epcas2p31c3deaea27ceca3ecc405395d2cd10d4@epcas2p3.samsung.com>
2025-03-18 2:23 ` [PATCH v2] printk/panic: Add option to allow non-panic CPUs to write to the ring buffer Donghyeok Choe
2025-03-20 15:27 ` Petr Mladek
2025-03-24 2:16 ` Donghyeok Choe [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=20250324021654.GA15429@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=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox