From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Xiaolong Wang <xiaolongw@mail.usf.edu>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Best practice to upgrade kernel
Date: Fri, 26 Apr 2019 15:35:24 -0400 [thread overview]
Message-ID: <30888.1556307324@turing-police> (raw)
In-Reply-To: <3CFD8D9A-EC79-47B3-A15F-5A27E6EA5B4D@mail.usf.edu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 681 bytes --]
On Fri, 26 Apr 2019 11:17:24 -0700, Xiaolong Wang said:
> I have a newbie question. I’m using a 3.18.66 kernel branch from Qualcomm.
> Over the year I’ve applied some of patched here and there manually.
> But It seems Qualcomm does not patch lot of newly released vulnerabilities. I
> would love to upgrade to the latest 3.18.138 (not 4.x)
> What is the best practice here?
Since you're being forced by Qualcomm to use 3.18, take it up with them.
What's this? You say you're not forced to do it? Well, there's two things you
can do:
1) Continue feeling the pain of running an old kernel
2) Fix the reason you're on 3.18, and get on a 4.x or 5.x kernel.
Your choice.
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-04-26 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 18:17 Best practice to upgrade kernel Xiaolong Wang
2019-04-26 19:35 ` Valdis Klētnieks [this message]
2019-04-26 20:11 ` Greg KH
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=30888.1556307324@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@kernelnewbies.org \
--cc=xiaolongw@mail.usf.edu \
/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).