From: Joerg Vehlow <lkml@jv-coder.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Miroslav Lichvar <mlichvar@redhat.com>,
John Stultz <john.stultz@linaro.org>
Subject: Re: [4.14] Failing selftest timer/adjtick
Date: Wed, 10 Feb 2021 14:07:21 +0100 [thread overview]
Message-ID: <239b8a9a-d550-11e3-4650-39ad5bd85013@jv-coder.de> (raw)
In-Reply-To: <YCPZA7nkGGDru3xw@kroah.com>
Hi Greg,
On 2/10/2021 2:00 PM, Greg KH wrote:
> Have you tried applying it to that tree to see if it solves your problem
> and works properly? If so, please feel free to provide a working
> backported copy, with your signed-off-by and we can consider it.
It can be applied without any changes and fixes the problem, but since I
have not a lot of knowledge about this subsystem, I don't know if this
breaks anything or if it requires other patches to be applied first, to
not break anything..
Maybe the authors of the patch can check this easily or maybe know it.
That's why I added them to the initial mail.
> But, why not just use 4.19 or newer on that system?
Why does an LTS version of 4.14 exist? Because the customer demands it :)
If the failing test was not one of the kernel selftest, I wouldn't
bother you with this...
Joerg
next prev parent reply other threads:[~2021-02-10 13:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 12:43 [4.14] Failing selftest timer/adjtick Joerg Vehlow
2021-02-10 13:00 ` Greg KH
2021-02-10 13:07 ` Joerg Vehlow [this message]
2021-02-10 13:19 ` Miroslav Lichvar
2021-02-10 18:59 ` Naresh Kamboju
2021-02-11 10:34 ` Joerg Vehlow
2021-02-11 10:33 ` Joerg Vehlow
2021-02-11 10:45 ` Greg KH
2021-02-11 10:59 ` Miroslav Lichvar
2021-02-18 7:05 ` Joerg Vehlow
2021-03-01 7:04 ` Joerg Vehlow
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=239b8a9a-d550-11e3-4650-39ad5bd85013@jv-coder.de \
--to=lkml@jv-coder.de \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=mingo@kernel.org \
--cc=mlichvar@redhat.com \
--cc=stable@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 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.