linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Cromie <jim.cromie@gmail.com>
To: jbaron@akamai.com, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org
Cc: Jim Cromie <jim.cromie@gmail.com>
Subject: [PATCH 0/2] DYNAMIC_DEBUG for 5.13
Date: Tue, 27 Apr 2021 19:00:29 -0600	[thread overview]
Message-ID: <20210428010031.571623-1-jim.cromie@gmail.com> (raw)

Heres 2 maintenance patches;
- a minor short-circuit optimization
- a cleanup of old cruft

Jim Cromie (2):
  dyndbg: avoid calling dyndbg_emit_prefix when it has no work
  dyndbg: drop uninformative vpr_info

 include/linux/dynamic_debug.h |  9 +++++++++
 lib/dynamic_debug.c           | 10 ++++++++--
 2 files changed, 17 insertions(+), 2 deletions(-)

-- 
2.30.2


             reply	other threads:[~2021-04-28  1:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28  1:00 Jim Cromie [this message]
2021-04-28  1:00 ` [PATCH 1/2] dyndbg: avoid calling dyndbg_emit_prefix when it has no work Jim Cromie
2021-04-29 21:03   ` Jason Baron
2021-05-02  2:49     ` jim.cromie
2021-04-28  1:00 ` [PATCH 2/2] dyndbg: drop uninformative vpr_info Jim Cromie

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=20210428010031.571623-1-jim.cromie@gmail.com \
    --to=jim.cromie@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jbaron@akamai.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;
as well as URLs for NNTP newsgroup(s).