lkml.org 
[lkml]   [2020]   [Nov]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Date
    SubjectRe: [PATCH 5.9 000/391] 5.9.4-rc1 review
    On Wed, 4 Nov 2020 at 16:28, Felipe Balbi <balbi@kernel.org> wrote:
    >
    >
    > Hi,
    >
    > Naresh Kamboju <naresh.kamboju@linaro.org> writes:
    >
    > > On Wed, 4 Nov 2020 at 02:07, Greg Kroah-Hartman
    > > <gregkh@linuxfoundation.org> wrote:
    > >>
    > >> This is the start of the stable review cycle for the 5.9.4 release.
    > >> There are 391 patches in this series, all will be posted as a response
    > >> to this one. If anyone has any issues with these being applied, please
    > >> let me know.
    > >>
    > >> Responses should be made by Thu, 05 Nov 2020 20:29:58 +0000.
    > >> Anything received after that time might be too late.
    > >>
    > >> The whole patch series can be found in one patch at:
    > >> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.9.4-rc1.gz
    > >> or in the git tree and branch at:
    > >> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.9.y
    > >> and the diffstat can be found below.
    > >>
    > >> thanks,
    > >>
    > >> greg k-h
    > >
    > > Results from Linaro’s test farm.
    > > No regressions on arm64, arm, x86_64, and i386.
    > >
    > > Tested-by: Linux Kernel Functional Testing <lkft@linaro.org>
    > >
    > > NOTE:
    > > The kernel warning noticed on arm64 nxp ls2088 device with KASAN config
    > > enabled while booting the device. We are not considering this as regression
    > > because this is the first arm64 KASAN config enabled on nxp ls2088 device.
    > >
    > > [ 3.301882] dwc3 3100000.usb3: Failed to get clk 'ref': -2
    > > [ 3.307433] ------------[ cut here ]------------
    > > [ 3.312048] dwc3 3100000.usb3: request value same as default, ignoring
    >
    > fix your DTS :-)

    Done.

    >
    > You're requesting to change a register value that shouldn't be changed
    > (it should be properly set during coreConsultant
    > instantiation). Whenever the requested value is the same as the reset
    > value of the register we WARN to let users know that the register
    > shouldn't be touched.

    Thanks for looking into this.
    The reported issue is a false alarm. please ignore.

    - Naresh

    \
     
     \ /
      Last update: 2020-11-04 12:19    [W:4.067 / U:0.876 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site