From: Petr Mladek <pmladek@suse.com>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: live-patching@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 2/3] selftests/livepatch: use $(dmesg --notime) instead of manually filtering
Date: Fri, 12 Jun 2020 12:12:24 +0200 [thread overview]
Message-ID: <20200612101224.GG4311@linux-b0ei> (raw)
In-Reply-To: <20200610172101.21910-3-joe.lawrence@redhat.com>
On Wed 2020-06-10 13:21:00, Joe Lawrence wrote:
> The dmesg utility already comes with a command line switch to omit
> kernel timestamps, let's use it instead of applying an extra regex to
> filter them out.
>
> Now without the '[timestamp]: ' prefix at the beginning of the log
> entry, revise the filtering regex to search for the 'livepatch:'
> subsystem prefix at the beginning of the line.
>
> Signed-off-by: Joe Lawrence <joe.lawrence@redhat.com>
Nice simplification.
Reviewed-by: Petr Mladek <pmladek@suse.com>
Best Regards,
Petr
next prev parent reply other threads:[~2020-06-12 10:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 17:20 [PATCH 0/3] selftests/livepatch: small script cleanups Joe Lawrence
2020-06-10 17:20 ` [PATCH 1/3] selftests/livepatch: Don't clear dmesg when running tests Joe Lawrence
2020-06-11 7:38 ` Miroslav Benes
2020-06-11 13:01 ` Joe Lawrence
2020-06-11 13:06 ` Miroslav Benes
2020-06-12 9:49 ` Petr Mladek
2020-06-14 15:19 ` Joe Lawrence
2020-06-12 10:11 ` Petr Mladek
2020-06-10 17:21 ` [PATCH 2/3] selftests/livepatch: use $(dmesg --notime) instead of manually filtering Joe Lawrence
2020-06-12 10:12 ` Petr Mladek [this message]
2020-06-10 17:21 ` [PATCH 3/3] selftests/livepatch: filter 'taints' from dmesg comparison Joe Lawrence
2020-06-11 7:39 ` Miroslav Benes
2020-06-11 13:10 ` Joe Lawrence
2020-06-12 11:47 ` Petr Mladek
2020-06-12 12:57 ` Kamalesh Babulal
2020-06-14 14:45 ` Joe Lawrence
2020-06-15 7:55 ` Miroslav Benes
2020-06-15 9:19 ` Petr Mladek
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=20200612101224.GG4311@linux-b0ei \
--to=pmladek@suse.com \
--cc=joe.lawrence@redhat.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=live-patching@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).