mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marcos Paulo de Souza <mpdesouza@suse.com>
To: Daniel Thompson <daniel@riscstar.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Petr Mladek	 <pmladek@suse.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	John Ogness	 <john.ogness@linutronix.de>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Jason Wessel <jason.wessel@windriver.com>,
	Daniel Thompson <danielt@kernel.org>,
	Douglas Anderson	 <dianders@chromium.org>,
	linux-kernel@vger.kernel.org,
		kgdb-bugreport@lists.sourceforge.net
Subject: Re: [PATCH v5 0/5] Handle NBCON consoles on KDB
Date: Thu, 02 Oct 2025 13:20:00 -0300	[thread overview]
Message-ID: <4b1eb94db3c0e43f935930fccae5726dc381ff9e.camel@suse.com> (raw)
In-Reply-To: <aN6FvQGj2w70Ejrz@aspen.lan>

githubOn Thu, 2025-10-02 at 15:01 +0100, Daniel Thompson wrote:
> On Tue, Sep 30, 2025 at 02:21:06PM -0300, Marcos Paulo de Souza
> wrote:
> > In v5 only patch three was changed, changing the check for KDB CPU,
> > as suggested
> > by Petr Mladek. Also, it was based on the recent panic API [2],
> > which now sits on
> > -mm tree.
> 
> Do you keep this work in a git tree anywhere? I wanted to point the
> kgdb
> test suite at it but the patches don't apply cleanly (even after I
> grabbed the patches mentioned in [2].

Yep... my mistake! I had rebased my patches on top on -mm tree just top
get those patches that I mentioned in [2], but then I rebased back to
master, which had some conflicts...

So, now I just pushed my changes on top on [2], which you can access
here[3]. I also included the revert of the code that converted 8250 to
NBCON, which is easier to test it using qemu, as I presented on the
cover-leter.

Thanks a lot for reviewing and testing the patchset!


[3]: https://github.com/marcosps/linux/tree/nbcon-kgdboc-v5

> 
> 
> Daniel.

      reply	other threads:[~2025-10-02 16:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30 17:21 Marcos Paulo de Souza
2025-09-30 17:21 ` [PATCH v5 1/5] printk: nbcon: Export console_is_usable Marcos Paulo de Souza
2025-10-01 14:36   ` John Ogness
2025-09-30 17:21 ` [PATCH v5 2/5] printk: nbcon: Introduce KDB helpers Marcos Paulo de Souza
2025-10-01 14:56   ` John Ogness
2025-10-02 11:23     ` Marcos Paulo de Souza
2025-10-02 19:03     ` Marcos Paulo de Souza
2025-10-06  8:31       ` John Ogness
2025-10-06 13:58     ` Petr Mladek
2025-09-30 17:21 ` [PATCH v5 3/5] printk: nbcon: Allow KDB to acquire the NBCON context Marcos Paulo de Souza
2025-10-01 15:05   ` John Ogness
2025-09-30 17:21 ` [PATCH v5 4/5] printk: nbcon: Export nbcon_write_context_set_buf Marcos Paulo de Souza
2025-10-01 15:08   ` John Ogness
2025-09-30 17:21 ` [PATCH v5 5/5] kdb: Adapt kdb_msg_write to work with NBCON consoles Marcos Paulo de Souza
2025-10-01 15:21   ` John Ogness
2025-10-02 14:01 ` [PATCH v5 0/5] Handle NBCON consoles on KDB Daniel Thompson
2025-10-02 16:20   ` Marcos Paulo de Souza [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=4b1eb94db3c0e43f935930fccae5726dc381ff9e.camel@suse.com \
    --to=mpdesouza@suse.com \
    --cc=daniel@riscstar.com \
    --cc=danielt@kernel.org \
    --cc=dianders@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jason.wessel@windriver.com \
    --cc=john.ogness@linutronix.de \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.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®