From: Will Deacon <will@kernel.org>
To: catalin.marinas@arm.com,
Lakshmi Ramasubramanian <nramas@linux.microsoft.com>,
robh@kernel.org, dan.carpenter@oracle.com
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, bauerman@linux.ibm.com,
qiuguorui1@huawei.com, kbuild@lists.01.org, lkp@intel.com
Subject: Re: [PATCH] arm64: kexec: Fix missing error code 'ret' warning in load_other_segments()
Date: Mon, 13 Dec 2021 16:42:45 +0000 [thread overview]
Message-ID: <163941287805.4004441.18442960905908913119.b4-ty@kernel.org> (raw)
In-Reply-To: <20211210010121.101823-1-nramas@linux.microsoft.com>
On Thu, 9 Dec 2021 17:01:21 -0800, Lakshmi Ramasubramanian wrote:
> Since commit ac10be5cdbfa ("arm64: Use common
> of_kexec_alloc_and_setup_fdt()"), smatch reports the following warning:
>
> arch/arm64/kernel/machine_kexec_file.c:152 load_other_segments()
> warn: missing error code 'ret'
>
> Return code is not set to an error code in load_other_segments() when
> of_kexec_alloc_and_setup_fdt() call returns a NULL dtb. This results
> in status success (return code set to 0) being returned from
> load_other_segments().
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: kexec: Fix missing error code 'ret' warning in load_other_segments()
https://git.kernel.org/arm64/c/4bfe24b6beb3
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
next prev parent reply other threads:[~2021-12-13 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 1:01 Lakshmi Ramasubramanian
2021-12-13 16:42 ` Will Deacon [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-09 0:45 Lakshmi Ramasubramanian
2021-12-09 9:08 ` Catalin Marinas
2021-12-09 16:32 ` Lakshmi Ramasubramanian
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=163941287805.4004441.18442960905908913119.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=bauerman@linux.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=dan.carpenter@oracle.com \
--cc=kbuild-all@lists.01.org \
--cc=kbuild@lists.01.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nramas@linux.microsoft.com \
--cc=qiuguorui1@huawei.com \
--cc=robh@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
all inboxes | Powered by JetHome®