linux-um archives
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Philip Li <philip.li@intel.com>,
	linux-um@lists.infradead.org, kbuild-all@01.org,
	LKP <lkp@intel.com>
Subject: Re: Testing UserModeLinux with kbuild bot
Date: Wed, 31 Oct 2018 11:15:54 +0100	[thread overview]
Message-ID: <2576349.EAEpUZHT3j@blindfold> (raw)
In-Reply-To: <20181031100743.wstzibltwysrmmgr@wfg-t540p.sh.intel.com>

Fengguang,

Am Mittwoch, 31. Oktober 2018, 11:07:43 CET schrieb Fengguang Wu:
> Hi Richard,
> 
> On Wed, Oct 31, 2018 at 09:45:57AM +0100, Richard Weinberger wrote:
> >Fengguang,
> >
> >I wonder what kind of tests currently are enabled for UML?
> >If I remember correctly we disabled some a few years ago.
> 
> Currently we are testing tree
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.git

good! Which branches linux-next and master?
 
Is it also possible to test patches which land on our mailinglist?

> There are no special settings for UML tree, so the standard build
> tests, static checks, boot tests and runtime tests will be performed.
> Note that there are no UML specific runtime test case.

Are you interested in rumtime tests?
Actually running a UML is pretty easy.
I can provide some command lines.

Thanks,
//richard



_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um


  reply	other threads:[~2018-10-31 10:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31  8:45 Testing UserModeLinux with kbuild bot Richard Weinberger
2018-10-31 10:07 ` Fengguang Wu
2018-10-31 10:15   ` Richard Weinberger [this message]
2018-10-31 10:34     ` Fengguang Wu
2018-10-31 10:43       ` Richard Weinberger
2018-10-31 14:36         ` Li, Philip

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=2576349.EAEpUZHT3j@blindfold \
    --to=richard@nod.at \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-um@lists.infradead.org \
    --cc=lkp@intel.com \
    --cc=philip.li@intel.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