Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Christos Gavros" <gavrosc@yahoo.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] host_dmesg_logger: dmesg diff on BuildStarted and BuildCompleted
Date: Tue, 01 Jul 2025 01:07:42 -0700	[thread overview]
Message-ID: <5366.1751357262764308701@lists.openembedded.org> (raw)
In-Reply-To: <a2b09f595589a62cb5dd4207d1d2b7f40afcfe2a.camel@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 162 bytes --]

hi

shall i prepare a v3 which will ignore KERN_INFO level and we run one more build?
Then i can go through the messages of this build again.

Br
Christos

[-- Attachment #2: Type: text/html, Size: 3011 bytes --]

  reply	other threads:[~2025-07-01  8:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250623171552.28824-1-gavrosc.ref@yahoo.com>
2025-06-23 17:15 ` [PATCH v2] host_dmesg_logger: dmesg diff on BuildStarted and BuildCompleted Christos Gavros
2025-06-23 21:18   ` [OE-core] " Richard Purdie
2025-06-24  5:59     ` Christos Gavros
     [not found]   ` <184BC8A6CD5551EF.5589@lists.openembedded.org>
2025-06-24  7:59     ` [OE-core] " Richard Purdie
2025-06-24  8:36       ` Alexandre Belloni
2025-06-24 20:16         ` Christos Gavros
2025-06-24 20:43           ` [OE-core] " Richard Purdie
2025-06-24 21:14             ` Christos Gavros
2025-06-24 22:33               ` [OE-core] " Richard Purdie
2025-06-25  5:50                 ` Christos Gavros
2025-07-01  7:11                   ` Christos Gavros
2025-07-01  7:57                     ` [OE-core] " Richard Purdie
2025-07-01  8:07                       ` Christos Gavros [this message]
2025-07-01  8:25                         ` Christos Gavros
     [not found]                     ` <184E1198346579D3.6792@lists.openembedded.org>
2025-07-01  8:00                       ` [OE-core] " Richard Purdie

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=5366.1751357262764308701@lists.openembedded.org \
    --to=gavrosc@yahoo.com \
    --cc=openembedded-core@lists.openembedded.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