live-patching.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: live-patching@vger.kernel.org, linux-kselftest@vger.kernel.org,
	Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
	Miroslav Benes <mbenes@suse.cz>, Yannick Cote <ycote@redhat.com>
Subject: Re: [PATCH v3 0/3] selftests/livepatch: small script cleanups
Date: Fri, 19 Jun 2020 11:06:42 +0200	[thread overview]
Message-ID: <20200619090641.GI3617@alley> (raw)
In-Reply-To: <20200618181040.21132-1-joe.lawrence@redhat.com>

On Thu 2020-06-18 14:10:37, Joe Lawrence wrote:
> Hi Petr,
> 
> Given the realization about kernel log timestamps and partial log
> comparison with v2, I respun a final version dropping the dmesg --notime
> patch, fixed any rebase conflicts, and added a comment per your
> suggestion.
> 
> I copied all the ack and review tags from v2 since the patchset is
> unchanged otherwise.  Hopefully this v3 minimizes any maintainer
> fiddling on your end.

Ah, I just waited a bit for eventual reaction and was going to push
the rebased version today.

Anyway, you made it easier from me. Also it is great the you
added the comment.

This patchset is commited in livepatching.git,
branch for-5.9/selftests-cleanup now.

Best Reagrds,
Petr

      parent reply	other threads:[~2020-06-19  9:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18 18:10 [PATCH v3 0/3] selftests/livepatch: small script cleanups Joe Lawrence
2020-06-18 18:10 ` [PATCH v3 1/3] selftests/livepatch: Don't clear dmesg when running tests Joe Lawrence
2020-06-18 18:10 ` [PATCH v3 2/3] selftests/livepatch: refine dmesg 'taints' in dmesg comparison Joe Lawrence
2020-06-18 18:10 ` [PATCH v3 3/3] selftests/livepatch: add test delimiter to dmesg Joe Lawrence
2020-06-19  9:06 ` Petr Mladek [this message]

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=20200619090641.GI3617@alley \
    --to=pmladek@suse.com \
    --cc=joe.lawrence@redhat.com \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=live-patching@vger.kernel.org \
    --cc=mbenes@suse.cz \
    --cc=ycote@redhat.com \
    /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).