From: Miroslav Benes <mbenes@suse.cz>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: live-patching@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, "Jiri Kosina" <jikos@kernel.org>,
"Josh Poimboeuf" <jpoimboe@redhat.com>,
"Petr Mladek" <pmladek@suse.com>,
"Libor Pecháček" <lpechacek@suse.com>,
"Nicolai Stange" <nstange@suse.de>,
"Artem Savkov" <asavkov@redhat.com>
Subject: Re: [PATCH v2] Add livepatch kselftests
Date: Thu, 12 Apr 2018 15:28:59 +0200 (CEST) [thread overview]
Message-ID: <alpine.LSU.2.21.1804121526110.4758@pobox.suse.cz> (raw)
In-Reply-To: <1523373354-10801-1-git-send-email-joe.lawrence@redhat.com>
> Questions for v3:
>
> - Should we split off the atomic replace and shadow variable update
> tests so that the this patchset could be merged before the ones
> listed above?
What Josh said. If we merge it almost together, there is no need to split
it.
> - I didn't remove any of the sample modules. If anyone thinks any of
> them should go, let me know. They serve as nice, simple examples so
> I thought they should all stay.
Ok
> - Module naming convention: to make the test script easier to grep
> module names and filenames, I broke with livepatch convention and
> used underscores instead of dashes. I didn't think it worth the
> regex foo to flip back and forth in the test script.
Ok
Miroslav
prev parent reply other threads:[~2018-04-12 13:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 15:15 Joe Lawrence
2018-04-10 15:15 ` [PATCH v2] selftests/livepatch: introduce tests Joe Lawrence
2018-04-10 20:00 ` Josh Poimboeuf
2018-04-10 20:50 ` Joe Lawrence
2018-04-10 21:33 ` Josh Poimboeuf
2018-04-10 21:38 ` Jiri Kosina
2018-04-11 3:44 ` kbuild test robot
2018-04-10 20:04 ` [PATCH v2] Add livepatch kselftests Josh Poimboeuf
2018-04-12 13:28 ` Miroslav Benes [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=alpine.LSU.2.21.1804121526110.4758@pobox.suse.cz \
--to=mbenes@suse.cz \
--cc=asavkov@redhat.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=lpechacek@suse.com \
--cc=nstange@suse.de \
--cc=pmladek@suse.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
all inboxes | Powered by JetHome®