linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: mbenes at suse.cz (Miroslav Benes)
Subject: [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
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: mbenes@suse.cz (Miroslav Benes)
Subject: [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)
Message-ID: <20180412132859.KH4rJZEkPe5TON4XlYUrzTX0lFWhuCF2wo8y-eGdIwQ@z> (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
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2018-04-12 13:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-10 15:15 [PATCH v2] Add livepatch kselftests joe.lawrence
2018-04-10 15:15 ` Joe Lawrence
2018-04-10 15:15 ` [PATCH v2] selftests/livepatch: introduce tests joe.lawrence
2018-04-10 15:15   ` Joe Lawrence
2018-04-10 20:00   ` jpoimboe
2018-04-10 20:00     ` Josh Poimboeuf
2018-04-10 20:50     ` joe.lawrence
2018-04-10 20:50       ` Joe Lawrence
2018-04-10 21:33       ` jpoimboe
2018-04-10 21:33         ` Josh Poimboeuf
2018-04-10 21:38         ` jikos
2018-04-10 21:38           ` Jiri Kosina
     [not found]   ` <201804111155.d856J7oR%fengguang.wu@intel.com>
2018-04-11 13:59     ` joe.lawrence
2018-04-11 13:59       ` Joe Lawrence
2018-04-13 15:49       ` [kbuild-all] " philip.li
2018-04-13 15:49         ` Philip Li
2018-04-13 20:55         ` joe.lawrence
2018-04-13 20:55           ` Joe Lawrence
2018-04-17  2:32           ` xiaolong.ye
2018-04-17  2:32             ` Ye Xiaolong
2018-04-10 20:04 ` [PATCH v2] Add livepatch kselftests jpoimboe
2018-04-10 20:04   ` Josh Poimboeuf
2018-04-12 13:28 ` mbenes [this message]
2018-04-12 13:28   ` Miroslav Benes

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=linux-kselftest@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).