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 1/3] dyndbg: fix spurious log-level change
Date: Thu, 14 Oct 2021 10:58:36 +0200 [thread overview]
Message-ID: <YWfxPLpBTQLzm6Bk@kroah.com> (raw)
In-Reply-To: <20211013220726.1280565-2-jim.cromie@gmail.com>
On Wed, Oct 13, 2021 at 04:07:24PM -0600, Jim Cromie wrote:
> HEAD~recent inadvertently altered a message's verbosity from 1 to 2, restore it.
I do not understand this changelog text at all.
And always wrap your changelog text at 72 columns, like your editor is
asking you to.
>
> Signed-off-By: Jim Cromie <jim.cromie@gmail.com>
Please put a proper "Fixes:" tag in here.
thanks,
greg k-h
next prev parent reply other threads:[~2021-10-14 8:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 22:07 [PATCH 0/3] dynamic debug for -next Jim Cromie
2021-10-13 22:07 ` [PATCH 1/3] dyndbg: fix spurious log-level change Jim Cromie
2021-10-14 8:58 ` Greg KH [this message]
2021-10-14 22:36 ` [PATCH 1/1] dyndbg: fix spurious vNpr_info change Jim Cromie
2021-10-13 22:07 ` [PATCH 2/3] dyndbg: vpr-info on remove-module complete, not starting Jim Cromie
2021-10-13 22:07 ` [PATCH 3/3] dyndbg: no vpr-info on empty queries 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=YWfxPLpBTQLzm6Bk@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;
as well as URLs for NNTP newsgroup(s).