From: Greg KH <gregkh@linuxfoundation.org>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: jbaron@akamai.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] dyndbg: refine export, rename to dynamic_debug_exec_queries()
Date: Fri, 28 Aug 2020 12:30:22 +0200 [thread overview]
Message-ID: <20200828103022.GD1470435@kroah.com> (raw)
In-Reply-To: <20200825173339.2082585-3-jim.cromie@gmail.com>
On Tue, Aug 25, 2020 at 11:33:38AM -0600, Jim Cromie wrote:
> commit 59cf47e7df31 dyndbg: export ddebug_exec_queries
> left a few configs broken, fix them with ifdef stub-fns.
Please use the standard way of printing commit ids, it's in the
submitting patches document.
>
> Rename the export to dynamic_debug_exec_queries(). This is a more
> canonical function name, instead of exposing the 'ddebug' internal
> name prefix. Do this now, before export hits v5.9.0
>
> Implement as new function wrapping ddebug_exec_queries(now static
> again), which copies the query-string, preserving ddebug_exec_queries'
> in-place parsing, while allowing users to pass const strings.
>
> --
> v2- fixes per Joe Perches
Shouldn't that go below the --- line?
>
> Signed-off-by: Jim Cromie <jim.cromie@gmail.com>
Can you put a "Fixes:" tag in here?
thanks,
greg k-h
next prev parent reply other threads:[~2020-08-28 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 17:33 [PATCH-v2 0/3] dynamic-debug fixups for 5.9 Jim Cromie
2020-08-25 17:33 ` [PATCH v2 1/3] dyndbg: give %3u width in pr-format, cosmetic only Jim Cromie
2020-08-25 17:33 ` [PATCH v2 2/3] dyndbg: refine export, rename to dynamic_debug_exec_queries() Jim Cromie
2020-08-28 10:30 ` Greg KH [this message]
2020-08-25 17:33 ` [PATCH v2 3/3] dyndbg: fix problem parsing format="foo bar" Jim Cromie
2020-08-28 0:16 ` [dyndbg] 738b8a92be: kernel_BUG_at_lib/dynamic_debug.c kernel test robot
2020-08-28 10:31 ` [PATCH v2 3/3] dyndbg: fix problem parsing format="foo bar" Greg KH
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=20200828103022.GD1470435@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