Live-Patching Archive on
 help / color / Atom feed
From: Joe Lawrence <>
To: shuah <>, Petr Mladek <>
	Jiri Benc <>
Subject: Re: [PATCH v3] selftests/livepatch: add test skip handling
Date: Wed, 24 Jul 2019 14:45:49 -0400
Message-ID: <> (raw)
In-Reply-To: <>

On 07/24/2019 12:45 PM, shuah wrote:
> On 7/24/19 12:27 AM, Petr Mladek wrote:
>> On Mon 2019-07-22 10:05:44, Joe Lawrence wrote:
>>> Add a skip() message function that stops the test, logs an explanation,
>>> and sets the "skip" return code (4).
>>> Before loading a livepatch self-test kernel module, first verify that
>>> we've built and installed it by running a 'modprobe --dry-run'.  This
>>> should catch a few environment issues, including !CONFIG_LIVEPATCH and
>>> !CONFIG_TEST_LIVEPATCH.  In these cases, exit gracefully with the new
>>> skip() function.
>>> Reported-by: Jiri Benc <>
>>> Suggested-by: Shuah Khan <>
>>> Signed-off-by: Joe Lawrence <>
>> Reviewed-by: Petr Mladek <>
>> Best Regards,
>> Petr
>> PS: No need to send v4. The missing "to", suggested by Shuah, could
>>      get added when pushing the patch into the repo.
> I can't make changes to the patch. I can adjust the commit log at times
> and correct merge conflicts.
> I would like to see v4 for this.

We should clarify for which tree this and "[PATCH] selftests/livepatch: 
push and pop dynamic debug config​" would be merged.  I had assumed this 
would go to the livepatching tree, but Shuah, do you prefer that 
selftest-centric patches go through the selftests tree?

I'm okay with either and can send up a v4 if needed.  But also this 
would be good to know for future changesets like this, we can perhaps 
mark the destination branch in advance.


-- Joe

  reply index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22 14:05 Joe Lawrence
2019-07-23 15:53 ` shuah
2019-07-24 20:05   ` [PATCH v4] " Joe Lawrence
2019-07-24 20:19     ` shuah
2019-07-24  6:27 ` [PATCH v3] " Petr Mladek
2019-07-24 16:45   ` shuah
2019-07-24 18:45     ` Joe Lawrence [this message]
2019-07-24 19:51       ` shuah

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Live-Patching Archive on

Archives are clonable:
	git clone --mirror live-patching/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 live-patching live-patching/ \
	public-inbox-index live-patching

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone