From: Greg KH <gregkh@linuxfoundation.org>
To: JH <jupiter.hce@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: Failed to connect to 4G modem
Date: Sat, 21 Sep 2019 06:45:10 +0200 [thread overview]
Message-ID: <20190921044510.GA990793@kroah.com> (raw)
In-Reply-To: <CAA=hcWR__j20ZQY9H8zzTryEatSfe+yXLYQXSaXMvgy3pwdJKg@mail.gmail.com>
On Sat, Sep 21, 2019 at 08:10:30AM +1000, JH wrote:
> Hi Greg,
>
> On 9/18/19, Greg KH <gregkh@linuxfoundation.org> wrote:
> > Otherwise, just use 5.3 now and then 5.4 when it comes out in a few
> > months.
>
> My apology for an off topic question. I discussed with my colleague to
> use 5.3, if we cannot wait for 5.4 LTS release, we will do a remote
> 5.4 upgrade from 5.3 on air for the product. One of my colleague
> warning me that kernel 5.3 and 5.4 LTS will not be a minor upgrade, it
> will be major upgrade which will have massive libraries changes. I
> don't agree with it, but I could not find kernel document to state
> either 5.3 and 5.4 LTS is a major or minor change. What is your
> insight view? Appreciate if you could point me a reference to prove my
> colleague is wrong.
You should never have to update any userspace code or library if the
kernel is updated as we guarantee backwards compatibility. If we did
break something, please let us know and we will work very hard to fix
it.
This is a guarantee we made back in 2007 or so, and have been sticking
to it since.
There is no "major" upgrade issue here, the kernel does a new release
every 3 months and changes the number, showing it is "newer" than the
previous one.
Hope this helps,
greg k-h
next prev parent reply other threads:[~2019-09-21 4:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 11:29 Failed to connect to 4G modem JH
2019-09-17 12:02 ` Greg KH
2019-09-17 21:38 ` JH
2019-09-18 1:43 ` Lars Melin
2019-09-18 5:47 ` Greg KH
2019-09-19 7:37 ` Bjørn Mork
2019-09-19 11:17 ` JH
2019-09-20 22:10 ` JH
2019-09-21 4:45 ` Greg KH [this message]
2019-09-22 22:17 ` JH
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=20190921044510.GA990793@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jupiter.hce@gmail.com \
--cc=linux-usb@vger.kernel.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).