[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241101182204.GA752705@aspen.lan>
Date: Fri, 1 Nov 2024 18:22:04 +0000
From: Daniel Thompson <daniel.thompson@...aro.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Doug Anderson <dianders@...omium.org>, linux-kernel@...r.kernel.org,
Masami Hiramatsu <mhiramat@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Yuran Pereira <yuran.pereira@...mail.com>,
Nir Lichtman <nir@...htman.org>
Subject: Re: [for-next][PATCH 03/11] kdb: Replace the use of simple_strto
with safer kstrto in kdb_main
On Fri, Nov 01, 2024 at 10:31:28AM -0400, Steven Rostedt wrote:
> On Fri, 1 Nov 2024 07:21:05 -0700
> Doug Anderson <dianders@...omium.org> wrote:
>
> > FWIW, I personally have no objection to this patch and patch #3/3 in
> > Nir's series (#5/11 in your email thread) going through the ftrace
> > tree, I'm not actually the maintainer of kdb/kgdb. I'm a reviewer and
> > I try my best to help, but officially you should probably have Daniel
> > Thompson's Ack for them. ...or at least make sure he's CCed here
> > saying that you've picked them up.
> >
> > I've added him to the conversation here.
>
> Sure, I can even drop this patch if need be. Thanks for adding Daniel to
> the Cc. I probably should have run these patches through get maintainers to
> make sure everyone was accounted for.
I haven't had a chance to review or hoover up the kdb/kgdb patches for
this cycle yet (mixture of travel and other things) but they are queued
up in my TODO list for next week.
I presume the tracing tree is involved because one of them changes the
kdb ftrace command? Are there dependencies between that and other
patches in the seriesm?
Daniel.
Powered by blists - more mailing lists