Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "HAGIO KAZUHITO(萩尾　一仁)" <k-hagio-ab@nec.com>
To: Edward Chron <echron@arista.com>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>
Cc: "colona@arista.com" <colona@arista.com>,
	"echron@gmail.com" <echron@gmail.com>
Subject: Re: [PATCH] makedumpfile add dmesg PRINTK_CALLER id support
Date: Wed, 24 Jan 2024 06:43:53 +0000	[thread overview]
Message-ID: <8640d3e2-81b5-d867-7a72-cad216208dfd@nec.com> (raw)
In-Reply-To: <97e8429c-0631-a085-f0c5-c1af91eb86e2@nec.com>

On 2024/01/11 15:55, HAGIO KAZUHITO(萩尾 一仁) wrote:
> On 2023/12/29 5:33, Edward Chron wrote:
>> Submission to Project: makedumpfile
>> Component: dmesg
>> Files: printk.c makedumpfile.c makedumpfile.h
>> Code level patch applied against: 1.7.4++ - latest code pulled from
>>       https://github.com/makedumpfile/makedumpfile
>> makedumpfile Issue #13
>>       https://github.com/makedumpfile/makedumpfile/issues/13
>> Project Owner: Kazuhito Hagio <k-hagio-ab@nec.com>
>> Revision: #1 on 2023/12/15 per Kazu ensure spacing of dmesg output
>>                              matches dmesg -S and new dmesg caller_id
>>                              output format (space after timestamp)
>> Revision: #2 on 2023/12/21 per Kazu use NOT_FOUND_STRUCTURE for caller_id
>> Revision: #3 on 2023/12/21 streamline code for printing caller_id
>> Revision: #4 on 2023/12/24 per Kazu make code consistent, drop the
>>                              CALLER_ID_SIZE not needed.
> 
> Thanks for the revision.  Looks good, will watch the util-linux status.

Thanks for the information that dmesg got the caller_id support.

Applied with a few tweaks.
https://github.com/makedumpfile/makedumpfile/commit/48bb1e089056

Thanks,
Kazu
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2024-01-24  6:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-28 20:33 [PATCH] makedumpfile add dmesg PRINTK_CALLER id support Edward Chron
2024-01-11  6:55 ` HAGIO KAZUHITO(萩尾　一仁)
2024-01-24  6:43   ` HAGIO KAZUHITO(萩尾　一仁) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-21 23:46 Edward Chron
2023-12-25  1:31 ` HAGIO KAZUHITO(萩尾　一仁)
2023-12-21 14:15 Edward Chron
2023-12-21 13:02 Edward Chron
2023-12-13 10:13 Edward Chron
2023-12-14  8:02 ` HAGIO KAZUHITO(萩尾　一仁)
2023-12-21  7:11   ` HAGIO KAZUHITO(萩尾　一仁)

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=8640d3e2-81b5-d867-7a72-cad216208dfd@nec.com \
    --to=k-hagio-ab@nec.com \
    --cc=colona@arista.com \
    --cc=echron@arista.com \
    --cc=echron@gmail.com \
    --cc=kexec@lists.infradead.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