public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Tom Rymes <trymes@rymes.com>
To: development@lists.ipfire.org
Subject: Core 121 - Updating machines using experimental kernels
Date: Wed, 13 Jun 2018 12:38:17 -0400	[thread overview]
Message-ID: <b506333c-63dd-bba3-c38b-44071811e707@rymes.com> (raw)

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

I have a few machines here running Arne's experimental kernels for 4.14. 
As I reported on the forum, they are still running well, but I wanted to 
ask whether any special changes will need to be made before upgrading to 
121 when it is released, such as rolling back to the standard kernel.

Many thanks,

Tom

             reply	other threads:[~2018-06-13 16:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-13 16:38 Tom Rymes [this message]
2018-06-13 21:49 ` Michael Tremer
2018-06-13 21:57   ` Tom Rymes

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=b506333c-63dd-bba3-c38b-44071811e707@rymes.com \
    --to=trymes@rymes.com \
    --cc=development@lists.ipfire.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