mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Javier Romero <linux.kernel.programming@gmail.com>
To: Ken Moffat <zarniwhoop@ntlworld.com>, linux-kernel@vger.kernel.org
Subject: Re: Contribution to Linux Kernel.
Date: Mon, 25 Sep 2017 16:03:14 -0300	[thread overview]
Message-ID: <6ad61767-7349-16ca-e5ec-1a7732d488d4@gmail.com> (raw)
In-Reply-To: <20170924202505.GA29877@milliways.localdomain>

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?

Regards,



Javi


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,
>>
>> Thank you for your answer.
>>
>> Will it be better to work with linux-next Kernel for testing?
>>
>> Regards.
>>
> 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.
>
> The -next kernels are transient - what is there today might be
> removed tomorrow, what is in linus's -rc kernels (and in point
> releases of stable kernels) usually remains unless somebody finds a
> showstopper bug.
>
> If you are testing -next, expect to find more problems : in theory
> everything which gets to Linus's tree has been through an amount of
> testing before he applies it.
>
> Most people have limited time to test kernels.  Build farms usually
> run boot tests on all of these kernels, but do very little testing
> of whether or not any particular use is worse than before.
>
> For any of these, expect problems to arise when least convenient to
> you.  I try to test linus's -rc kernels on my own hardware,
> typically not until at least -rc2, and then once or twice after
> that.
>
> On occasion I test patchsets which look interesting, usually I end
> up wishing I had not bothered (they claim to help things, but do
> little or nothing for my machines).
>
> The other problem with testing, when you do find a real issue, is
> making sure it is repeatable so that you can bisect reliably.
>
> In short, test what interests you.  It's like writing or fixing
> code for the kernel as a hobby - work on what matters to you.
> Getting enough experience and visibility to become paid to code is a
> different thing entirely, I can't advise on that.
>
> So, for me it is just a hobby (with a side order of "hope this new
> release doesn't break anything for me").
>
> If you are not being paid for it, try to enjoy it.
>
> ĸen

       reply	other threads:[~2017-09-25 19:03 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 [this message]
     [not found]     ` <CGME20170926091446eucas1p2bfc9dc15d691adef218a5bc49941e633@eucas1p2.samsung.com>
2017-09-26  9:14       ` Kamil Konieczny
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=6ad61767-7349-16ca-e5ec-1a7732d488d4@gmail.com \
    --to=linux.kernel.programming@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

Powered by JetHome