From: Greg KH <gregkh@linuxfoundation.org>
To: jim.cromie@gmail.com
Cc: Jason Baron <jbaron@akamai.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/6] dyndbg updates for 5.15-rcX
Date: Fri, 1 Oct 2021 09:38:18 +0200 [thread overview]
Message-ID: <YVa66i8xoRAu6/NZ@kroah.com> (raw)
In-Reply-To: <CAJfuBxxhoEs6z+HQ-ts55TbzfuVvxh=YPtEjqnqB6ZOOgiiMBw@mail.gmail.com>
On Thu, Sep 30, 2021 at 03:33:44PM -0600, jim.cromie@gmail.com wrote:
> On Thu, Sep 30, 2021 at 12:06 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Wed, Sep 29, 2021 at 12:37:29PM -0600, Jim Cromie wrote:
> > > Hi Jason, Greg,
> > >
> > > Heres a set of "maintenance" patches distilled out of other work. Its
> > > almost all tweaks to verbose output, except for 1st, which changes a
> > > strcmp to == because its true, and useful going forward.
> > >
> > > Jim Cromie (6):
> > > dyndbg: recode for stronger precondition
> > > dyndbg: show module in vpr-info in dd-exec-queries
> > > dyndbg: rationalize verbosity
> > > dyndbg: use alt-quotes in vpr-infos, not those user might use
> > > dyndbg: vpr-info on remove-module complete, not starting
> > > dyndbg: no vpr-info on empty queries
> > >
> > > .../admin-guide/dynamic-debug-howto.rst | 2 +-
> > > lib/dynamic_debug.c | 47 ++++++++++---------
> > > 2 files changed, 26 insertions(+), 23 deletions(-)
> >
> > Are these real bug fixes that have to get into 5.15-final? They seem
> > like 5.16-rc1 patches instead.
> >
>
> not real bug fixes.
> I thought maybe theyre low-risk enough, maybe on rc1+, but I was late.
Then please do not force me to be the one to push back, you know the
development model...
> I'll try to hit the window right for 5.16
So do you want me to pick these up now for my -next branch to get proper
testing in time for 5.16-rc1?
thanks,
greg k-h
prev parent reply other threads:[~2021-10-01 7:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 18:37 [PATCH 0/6] dyndbg updates for 5.15-rcX Jim Cromie
2021-09-29 18:37 ` [PATCH 1/6] dyndbg: recode for stronger precondition Jim Cromie
2021-09-30 6:06 ` Greg KH
2021-09-29 18:37 ` [PATCH 2/6] dyndbg: show module in vpr-info in dd-exec-queries Jim Cromie
2021-09-29 18:37 ` [PATCH 3/6] dyndbg: rationalize verbosity Jim Cromie
2021-09-30 6:10 ` Greg KH
2021-10-02 20:58 ` jim.cromie
2021-09-29 18:37 ` [PATCH 4/6] dyndbg: use alt-quotes in vpr-infos, not those user might use Jim Cromie
2021-09-29 18:37 ` [PATCH 5/6] dyndbg: vpr-info on remove-module complete, not starting Jim Cromie
2021-09-29 18:37 ` [PATCH 6/6] dyndbg: no vpr-info on empty queries Jim Cromie
2021-09-30 6:05 ` [PATCH 0/6] dyndbg updates for 5.15-rcX Greg KH
2021-09-30 21:33 ` jim.cromie
2021-10-01 7:38 ` Greg KH [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=YVa66i8xoRAu6/NZ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jbaron@akamai.com \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.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