All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Xiaolong Wang <xiaolongw@mail.usf.edu>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Best practice to upgrade kernel
Date: Fri, 26 Apr 2019 22:11:15 +0200	[thread overview]
Message-ID: <20190426201115.GA6767@kroah.com> (raw)
In-Reply-To: <3CFD8D9A-EC79-47B3-A15F-5A27E6EA5B4D@mail.usf.edu>

On Fri, Apr 26, 2019 at 11:17:24AM -0700, Xiaolong Wang wrote:
> 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? 

Merge your branch with the android-common 3.18 branch, and try to run
that.  Note, there will be some conflicts, and I think there's a random
qualcomm branch somewhere on code aurora somewhere that has those
problems resolved if you have problems with them.

good luck, it's possible to do (I have a phone running the latest 3.18
release on it with a qcom chipset), but it all depends on exactly what
device you have as to how easy/hard it is going to be!

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      parent reply	other threads:[~2019-04-26 20:11 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
2019-04-26 20:11 ` Greg KH [this message]

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=20190426201115.GA6767@kroah.com \
    --to=greg@kroah.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.