From: Kamil Konieczny <k.konieczny@partner.samsung.com>
To: Javier Romero <linux.kernel.programming@gmail.com>,
Ken Moffat <zarniwhoop@ntlworld.com>,
linux-kernel@vger.kernel.org
Subject: Re: Contribution to Linux Kernel.
Date: Tue, 26 Sep 2017 11:14:39 +0200 [thread overview]
Message-ID: <539773e0-9527-daf2-e8f7-a2aff7d257a2@partner.samsung.com> (raw)
In-Reply-To: <6ad61767-7349-16ca-e5ec-1a7732d488d4@gmail.com>
On 25.09.2017 21:03, Javier Romero wrote:
> Hi,
>
> Last question, it will be the same to do Kernel testing on a virtual machine,
> or it will be better to do kernel testing over a no virtual machine?
>
> El 24/09/17 a las 17:25, Ken Moffat escribió:
>> On Sun, Sep 24, 2017 at 12:52:08PM -0300, Javier Romero wrote:
>>> Hi Ken,
>>>
>>> Will it be better to work with linux-next Kernel for testing?
>>>
>> Yes, no, maybe. I can't say what will work (process) for you, it
>> depends in part on what you want to test, and how flakey that is at
>> any particular time.
>>[...]
both tests will be different, because VM is not bare metal machine
and both will be valueable
Regards,
Kamil
next prev parent reply other threads:[~2017-09-26 9:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <59c7d4aa.d367370a.d4b44.16d6@mx.google.com>
[not found] ` <20170924202505.GA29877@milliways.localdomain>
2017-09-25 19:03 ` Javier Romero
[not found] ` <CGME20170926091446eucas1p2bfc9dc15d691adef218a5bc49941e633@eucas1p2.samsung.com>
2017-09-26 9:14 ` Kamil Konieczny [this message]
2017-09-26 14:52 ` Javier Romero
2017-10-23 9:29 ` Pavel Machek
2017-10-25 18:48 ` Javier Romero
[not found] ` <CAEH__nEMvScfyOanMUKrrQgq5PSueFhRoWM3YUd+3d2TSWyHWA@mail.gmail.com>
2017-11-15 10:40 ` Pavel Machek
2017-09-23 22:21 Javier Romero
-- strict thread matches above, loose matches on Subject: below --
2017-09-21 21:16 Javier Romero
[not found] ` <CGME20170922100216eucas1p240221e0bf388e43f463d12a0eec86941@eucas1p2.samsung.com>
2017-09-22 10:02 ` Kamil Konieczny
2017-09-22 12:51 ` Javier Romero
2017-09-22 19:15 ` Jonathan Corbet
2017-09-22 22:33 ` Javier Romero
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=539773e0-9527-daf2-e8f7-a2aff7d257a2@partner.samsung.com \
--to=k.konieczny@partner.samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.kernel.programming@gmail.com \
--cc=zarniwhoop@ntlworld.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®