[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAD=FV=XJAAz1a0DJF0f23e+6SPWrNW2EbhWp5xiq40OCLu4m5w@mail.gmail.com>
Date: Mon, 12 Jul 2021 06:40:59 -0700
From: Doug Anderson <dianders@...omium.org>
To: Sumit Garg <sumit.garg@...aro.org>
Cc: kgdb-bugreport@...ts.sourceforge.net,
Daniel Thompson <daniel.thompson@...aro.org>,
Jason Wessel <jason.wessel@...driver.com>,
Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...hat.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 1/4] kdb: Rename struct defcmd_set to struct kdb_macro_t
Hi,
On Mon, Jul 12, 2021 at 12:13 AM Sumit Garg <sumit.garg@...aro.org> wrote:
>
> > > @@ -671,7 +671,7 @@ static int kdb_exec_defcmd(int argc, const char **argv);
> > >
> > > static int kdb_defcmd2(const char *cmdstr, const char *argv0)
> > > {
> > > - struct defcmd_set *s = defcmd_set + defcmd_set_count - 1;
> > > + struct kdb_macro_t *s = kdb_macro + kdb_macro_count - 1;
> >
> > I guess the variable "s" was short for "set". Should it change to "m"
> > ? Here and in other places below.
> >
>
> This variable is dropped in patch #3. Can we bear this variable name
> until that patch?
Sure.
-Doug
Powered by blists - more mailing lists