linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Sjoerd <sjoerd@sjomar.eu>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Latest kernel to use?
Date: Fri, 25 Sep 2015 13:51:34 +0000	[thread overview]
Message-ID: <20150925135134.GF3749@carfax.org.uk> (raw)
In-Reply-To: <3800342.Pn9bHBFuTx@hoefnix>

[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]

On Fri, Sep 25, 2015 at 03:36:18PM +0200, Sjoerd wrote:
> Thanks all for the feedback. Still doubting though to go for 4.2.1 or not. 
> Main reason is that I am currently running 4.1.7 on my laptop which seems to 
> work fine and had some issues with the 4.2.0 kernel. No issues I thing that 
> were btrfs related, but more related to my nvidia card. Anyway switching back 
> to 4.1.7 resolved those, so I am a bit holding back to try the 4.2.1 version 
> ;)
> Anyway I'll see and can always revert back if I don't like it ;)

   If 4.1.7 is working OK for you, stick with it. It's getting much
less important now, as btrfs matures, to keep up with the _very_
latest. Purely on gut feeling about issues we see on IRC and here,
3.19 or later would be reasonable at the moment.

   Compared to, say, 3 or 4 years ago when running late -rc kernels
was often preferable to running the latest stable, and things have
improved quite a bit. :)

   Hugo.

-- 
Hugo Mills             | For months now, we have been making triumphant
hugo@... carfax.org.uk | retreats before a demoralised enemy who is advancing
http://carfax.org.uk/  | in utter disorder.
PGP: E2AB1DE4          |                              Eric Frank Russell, Wasp

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2015-09-25 13:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 21:07 Latest kernel to use? Sjoerd
2015-09-24 21:18 ` Hugo Mills
2015-09-25 11:20 ` Austin S Hemmelgarn
2015-09-25 13:12   ` Rich Freeman
2015-09-25 13:43     ` Roman Mamedov
     [not found]     ` <CAEp_DRB7zaHmJnghJzVR++_OO+4mrM_+jCjrYAQJcNUXpM=bAQ@mail.gmail.com>
2015-09-25 17:00       ` Rich Freeman
2015-09-25 17:41         ` Bostjan Skufca
2015-09-25 13:36 ` Sjoerd
2015-09-25 13:51   ` Hugo Mills [this message]
2015-09-25 14:34     ` Bostjan Skufca
2015-09-26  2:04       ` Duncan
2015-09-25 14:35     ` Sjoerd

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=20150925135134.GF3749@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sjoerd@sjomar.eu \
    /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).