All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	conor@kernel.org, allen.lkml@gmail.com
Subject: Re: [PATCH 6.1 000/366] 6.1.64-rc4 review
Date: Tue, 28 Nov 2023 15:45:52 +0000	[thread overview]
Message-ID: <2023112838-blandness-exodus-5ff8@gregkh> (raw)
In-Reply-To: <20231128-perceive-impulsive-754e8e2e2bbf@wendy>

On Tue, Nov 28, 2023 at 11:38:30AM +0000, Conor Dooley wrote:
> On Sun, Nov 26, 2023 at 03:46:28PM +0000, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.1.64 release.
> > There are 366 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.
> 
> I missed testing 6.1.63 so I noticed this only here, but my CI is
> complaining about seeing some
> [    0.000000] Couldn't find cpu id for hartid [0]
> during boot.
> 
> It was caused by
> 
> commit 3df98bd3196665f2fd37fcc5b2d483a24a314095
> Author: Anup Patel <apatel@ventanamicro.com>
> Date:   Fri Oct 27 21:12:53 2023 +0530
> 
>     RISC-V: Don't fail in riscv_of_parent_hartid() for disabled HARTs
>     
>     [ Upstream commit c4676f8dc1e12e68d6511f9ed89707fdad4c962c ]
>     
>     The riscv_of_processor_hartid() used by riscv_of_parent_hartid() fails
>     for HARTs disabled in the DT. This results in the following warning
>     thrown by the RISC-V INTC driver for the E-core on SiFive boards:
>     
>     [    0.000000] riscv-intc: unable to find hart id for /cpus/cpu@0/interrupt-controller
>     
>     The riscv_of_parent_hartid() is only expected to read the hartid
>     from the DT so we directly call of_get_cpu_hwid() instead of calling
>     riscv_of_processor_hartid().
>     
>     Fixes: ad635e723e17 ("riscv: cpu: Add 64bit hartid support on RV64")
>     Signed-off-by: Anup Patel <apatel@ventanamicro.com>
>     Reviewed-by: Atish Patra <atishp@rivosinc.com>
>     Link: https://lore.kernel.org/r/20231027154254.355853-2-apatel@ventanamicro.com
>     Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
>     Signed-off-by: Sasha Levin <sashal@kernel.org>
> 
> and there is already a fix for this in Linus' tree though that you can
> pick:
> 52909f176802 ("RISC-V: drop error print from riscv_hartid_to_cpuid()")
> 
> That's just one error print that realistically has no impact on the
> operation of the system, and is not introduced by this particular
> version, so
> 
> Tested-by: Conor Dooley <conor.dooley@microchip.com>

Thanks, I'll go queue that patch up now too, can't hurt :)

greg k-h

  reply	other threads:[~2023-11-28 15:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-26 15:46 [PATCH 6.1 000/366] 6.1.64-rc4 review Greg Kroah-Hartman
2023-11-26 17:16 ` SeongJae Park
2023-11-26 18:22 ` Pavel Machek
2023-11-27  4:14 ` Florian Fainelli
2023-11-27 18:13 ` Nam Cao
2023-11-27 19:25 ` Naresh Kamboju
2023-11-27 23:26 ` Jon Hunter
2023-11-28  2:53 ` Guenter Roeck
2023-11-28 11:38 ` Conor Dooley
2023-11-28 15:45   ` Greg Kroah-Hartman [this message]
2023-11-28 13:25 ` Allen
2023-11-28 21:01 ` Pavel Machek

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=2023112838-blandness-exodus-5ff8@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=allen.lkml@gmail.com \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.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.