public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: linux-kernel@vger.kernel.org, jbaron@akamai.com
Subject: Re: [PATCH 00/11] DYNAMIC_DEBUG for this cycle
Date: Thu, 1 Sep 2022 18:10:31 +0200	[thread overview]
Message-ID: <YxDZd8MQtrTLLNmC@kroah.com> (raw)
In-Reply-To: <20220811173541.2901122-1-jim.cromie@gmail.com>

On Thu, Aug 11, 2022 at 11:35:30AM -0600, Jim Cromie wrote:
> Hi Greg, Jason,
> 
> Please consider these for this rc-cycle.
>   - 1-9 have Jason's Ack,
>   - 9th removes unused EXPORTed fn.
>   - 10 is simple var cleanup
>   - 11 is a partial decoupling of dyndbg from kernel/module
> 
> Jim Cromie (11):
>   dyndbg: fix static_branch manipulation
>   dyndbg: fix module.dyndbg handling
>   dyndbg: show both old and new in change-info
>   dyndbg: reverse module walk in cat control
>   dyndbg: reverse module.callsite walk in cat control
>   dyndbg: use ESCAPE_SPACE for cat control
>   dyndbg: let query-modname override actual module name
>   dyndbg: add test_dynamic_debug module
>   dyndbg: drop EXPORTed dynamic_debug_exec_queries
>   dyndbg: cleanup auto vars in dynamic_debug_init
>   dyndbg: create and use struct _ddebug_info
> 
>  MAINTAINERS                   |   2 +
>  include/linux/dynamic_debug.h |  22 ++----
>  kernel/module/internal.h      |   4 +-
>  kernel/module/main.c          |  18 ++---
>  lib/Kconfig.debug             |  10 +++
>  lib/Makefile                  |   1 +
>  lib/dynamic_debug.c           | 141 +++++++++++++++++-----------------
>  lib/test_dynamic_debug.c      |  70 +++++++++++++++++
>  8 files changed, 172 insertions(+), 96 deletions(-)
>  create mode 100644 lib/test_dynamic_debug.c
> 
> -- 
> 2.37.1
> 

Is this still ok for linux-next now to go into 6.1-rc1?

Or does it need to be rebased?

thanks,

greg k-h

      parent reply	other threads:[~2022-09-01 16:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11 17:35 [PATCH 00/11] DYNAMIC_DEBUG for this cycle Jim Cromie
2022-08-11 17:35 ` [PATCH 01/11] dyndbg: fix static_branch manipulation Jim Cromie
2022-08-11 17:35 ` [PATCH 02/11] dyndbg: fix module.dyndbg handling Jim Cromie
2022-08-11 17:35 ` [PATCH 03/11] dyndbg: show both old and new in change-info Jim Cromie
2022-08-11 17:35 ` [PATCH 04/11] dyndbg: reverse module walk in cat control Jim Cromie
2022-08-11 17:35 ` [PATCH 05/11] dyndbg: reverse module.callsite " Jim Cromie
2022-08-11 17:35 ` [PATCH 06/11] dyndbg: use ESCAPE_SPACE for " Jim Cromie
2022-08-11 17:35 ` [PATCH 07/11] dyndbg: let query-modname override actual module name Jim Cromie
2022-08-11 17:35 ` [PATCH 08/11] dyndbg: add test_dynamic_debug module Jim Cromie
2022-08-11 17:35 ` [PATCH 09/11] dyndbg: drop EXPORTed dynamic_debug_exec_queries Jim Cromie
2022-08-11 17:35 ` [PATCH 10/11] dyndbg: cleanup auto vars in dynamic_debug_init Jim Cromie
2022-08-11 17:35 ` [PATCH 11/11] dyndbg: create and use struct _ddebug_info Jim Cromie
2022-08-12  5:37 ` [PATCH 00/11] DYNAMIC_DEBUG for this cycle Greg KH
2022-09-01 16:10 ` 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=YxDZd8MQtrTLLNmC@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