live-patching.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: Miroslav Benes <mbenes@suse.cz>,
	jpoimboe@redhat.com, pmladek@suse.com, shuah@kernel.org,
	live-patching@vger.kernel.org
Subject: Re: [PATCH] selftests/livepatch: Do not check order when using "comm" for dmesg checking
Date: Wed, 14 Oct 2020 23:53:13 +0200 (CEST)	[thread overview]
Message-ID: <nycvar.YFH.7.76.2010142352470.18859@cbobk.fhfr.pm> (raw)
In-Reply-To: <bd7b15d6-1796-9fb4-bf52-14bcd981458d@redhat.com>

On Wed, 14 Oct 2020, Joe Lawrence wrote:

> >> Acked-by: Joe Lawrence <joe.lawrence@redhat.com>
> >>
> >> And not so important for selftests, but helpful for backporting efforts:
> >>
> >> Fixes: 2f3f651f3756 ("selftests/livepatch: Use "comm" instead of "diff" for
> >> dmesg")
> > 
> > I've added the Fixes: tag and applied to for-5.9/upstream-fixes. Thanks,
> > 
> 
> Hi Jiri,
> 
> I was looking at a list of livepatching commits that went into 5.9 for
> backporting and was wondering if we ever merged this one?
> 
> It's not a show-stopper, but would be nice to get this one in for 5.10 if
> possible.

Hi Joe,

it was not enough of a trigger to actually send 5.9-rc pull request. But 
in cases like this, for-5.x/upstream-fixes branch gets included in 5.x+1 
pull request. So it absolutely will land in 5.10.

Thanks,

-- 
Jiri Kosina
SUSE Labs


  reply	other threads:[~2020-10-14 21:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-27 11:07 [PATCH] selftests/livepatch: Do not check order when using "comm" for dmesg checking Miroslav Benes
2020-08-27 13:20 ` Joe Lawrence
2020-08-27 13:28   ` Jiri Kosina
2020-10-14 21:48     ` Joe Lawrence
2020-10-14 21:53       ` Jiri Kosina [this message]
2020-10-14 22:15         ` Joe Lawrence

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=nycvar.YFH.7.76.2010142352470.18859@cbobk.fhfr.pm \
    --to=jikos@kernel.org \
    --cc=joe.lawrence@redhat.com \
    --cc=jpoimboe@redhat.com \
    --cc=live-patching@vger.kernel.org \
    --cc=mbenes@suse.cz \
    --cc=pmladek@suse.com \
    --cc=shuah@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).