From: Xiaolong Wang <xiaolongw@mail.usf.edu>
To: kernelnewbies@kernelnewbies.org
Subject: Best practice to upgrade kernel
Date: Fri, 26 Apr 2019 11:17:24 -0700 [thread overview]
Message-ID: <3CFD8D9A-EC79-47B3-A15F-5A27E6EA5B4D@mail.usf.edu> (raw)
Hi all,
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?
Thanks
-Dan
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2019-04-26 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 18:17 Xiaolong Wang [this message]
2019-04-26 19:35 ` Best practice to upgrade kernel Valdis Klētnieks
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=3CFD8D9A-EC79-47B3-A15F-5A27E6EA5B4D@mail.usf.edu \
--to=xiaolongw@mail.usf.edu \
--cc=kernelnewbies@kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).