From: Greg KH <gregkh@linux-foundation.org>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
Markus Trippelsdorf <markus@trippelsdorf.de>
Subject: Re: [PATCH] dyndbg: fix for SOH in logging messages
Date: Sat, 18 Aug 2012 23:13:52 -0700 [thread overview]
Message-ID: <20120819061352.GA1971@kroah.com> (raw)
In-Reply-To: <1345336551-10066-1-git-send-email-jim.cromie@gmail.com>
On Sat, Aug 18, 2012 at 06:35:51PM -0600, Jim Cromie wrote:
> commit af7f2158fde was done against master, and clashed with structured logging's change of KERN_LEVEL to SOH.
>
> Bisected and fixed by Markus Trippelsdorf.
>
> CC: Markus Trippelsdorf <markus@trippelsdorf.de>
> Signed-off-by: Jim Cromie <jim.cromie@gmail.com>
> ---
> drivers/base/core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/base/core.c b/drivers/base/core.c
> index cdd01c5..5e6e00b 100644
> --- a/drivers/base/core.c
> +++ b/drivers/base/core.c
> @@ -1912,8 +1912,8 @@ int __dev_printk(const char *level, const struct device *dev,
> "DEVICE=+%s:%s", subsys, dev_name(dev));
> }
> skip:
> - if (level[3])
> - level_extra = &level[3]; /* skip past "<L>" */
> + if (level[2])
> + level_extra = &level[2]; /* skip past KERN_SOH "L" */
>
> return printk_emit(0, level[1] - '0',
> dictlen ? dict : NULL, dictlen,
No, this still doesn't resolve the issue for me, it still looks like it
did before this patch (exactly the same to be exact.)
I do seem to get the correct output if I revert your original patch
(af7f2158fde), should I just do that instead?
greg k-h
next prev parent reply other threads:[~2012-08-19 6:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-19 0:35 [PATCH] dyndbg: fix for SOH in logging messages Jim Cromie
2012-08-19 6:13 ` Greg KH [this message]
2012-08-19 6:33 ` Greg KH
2012-08-19 6:37 ` 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=20120819061352.GA1971@kroah.com \
--to=gregkh@linux-foundation.org \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=torvalds@linux-foundation.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).