All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Mukesh Pilaniya <mpilaniy@redhat.com>
Cc: linux-riscv@lists.infradead.org, catalin.marinas@arm.com,
	will@kernel.org, mark.rutland@arm.com, chenhuacai@kernel.org,
	kernel@xen0n.name, pjw@kernel.org, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, alex@ghiti.fr, akpm@linux-foundation.org,
	baoquan.he@linux.dev, rppt@kernel.org, pasha.tatashin@soleen.com,
	pratyush@kernel.org, ltao@redhat.com, prudo@redhat.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
	kexec@lists.infradead.org, include@grrlz.net
Subject: Re: [PATCH v3 0/2] kexec: fix probe error codes and error propagation
Date: Sun, 01 Nov 2026 22:15:54 +0000	[thread overview]
Message-ID: <179357135454.2624073.2428991164390583415.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260821-mpilaniy-v3-0-76b355399d2e@redhat.com>

Hello:

This series was applied to riscv/linux.git (fixes)
by Mike Rapoport (Microsoft) <rppt@kernel.org>:

On Fri, 21 Aug 2026 19:19:56 +0530 you wrote:
> While debugging a misleading error on s390x where kexec -s reported
> "syscall kexec_file_load not available" instead of the actual EINVAL
> from a kernel command line that exceeded the architecture limit, we
> found that some kexec image probe functions return -EINVAL instead of
> -ENOEXEC for format mismatches, and kexec_image_probe_default() has a
> bug where it returns whatever the last loader returned rather than
> always returning -ENOEXEC when no loader matches.
> 
> [...]

Here is the summary with links:
  - [v3,1/2] kexec: return -ENOEXEC from image probe functions on mismatch
    https://git.kernel.org/riscv/c/2792b4b15f14
  - [v3,2/2] kexec: fix error propagation in kexec_image_probe_default()
    https://git.kernel.org/riscv/c/b7c94f4d0961

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html




WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Mukesh Pilaniya <mpilaniy@redhat.com>
Cc: linux-riscv@lists.infradead.org, catalin.marinas@arm.com,
	will@kernel.org, mark.rutland@arm.com, chenhuacai@kernel.org,
	kernel@xen0n.name, pjw@kernel.org, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, alex@ghiti.fr, akpm@linux-foundation.org,
	baoquan.he@linux.dev, rppt@kernel.org, pasha.tatashin@soleen.com,
	pratyush@kernel.org, ltao@redhat.com, prudo@redhat.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
	kexec@lists.infradead.org, include@grrlz.net
Subject: Re: [PATCH v3 0/2] kexec: fix probe error codes and error propagation
Date: Sun, 01 Nov 2026 22:15:54 +0000	[thread overview]
Message-ID: <179357135454.2624073.2428991164390583415.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260821-mpilaniy-v3-0-76b355399d2e@redhat.com>

Hello:

This series was applied to riscv/linux.git (fixes)
by Mike Rapoport (Microsoft) <rppt@kernel.org>:

On Fri, 21 Aug 2026 19:19:56 +0530 you wrote:
> While debugging a misleading error on s390x where kexec -s reported
> "syscall kexec_file_load not available" instead of the actual EINVAL
> from a kernel command line that exceeded the architecture limit, we
> found that some kexec image probe functions return -EINVAL instead of
> -ENOEXEC for format mismatches, and kexec_image_probe_default() has a
> bug where it returns whatever the last loader returned rather than
> always returning -ENOEXEC when no loader matches.
> 
> [...]

Here is the summary with links:
  - [v3,1/2] kexec: return -ENOEXEC from image probe functions on mismatch
    https://git.kernel.org/riscv/c/2792b4b15f14
  - [v3,2/2] kexec: fix error propagation in kexec_image_probe_default()
    https://git.kernel.org/riscv/c/b7c94f4d0961

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2026-11-01 22:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21 13:49 [PATCH v3 0/2] kexec: fix probe error codes and error propagation Mukesh Pilaniya
2026-08-21 13:49 ` Mukesh Pilaniya
2026-08-21 13:49 ` [PATCH v3 1/2] kexec: return -ENOEXEC from image probe functions on mismatch Mukesh Pilaniya
2026-08-21 13:49   ` Mukesh Pilaniya
2026-08-24 14:07   ` Will Deacon
2026-08-24 14:07     ` Will Deacon
2026-08-25  5:13     ` Mukesh Pilaniya
2026-08-25  5:13       ` Mukesh Pilaniya
2026-08-25 15:14       ` Will Deacon
2026-08-25 15:14         ` Will Deacon
2026-08-26 15:51         ` Mukesh Pilaniya
2026-08-26 15:51           ` Mukesh Pilaniya
2026-08-21 13:49 ` [PATCH v3 2/2] kexec: fix error propagation in kexec_image_probe_default() Mukesh Pilaniya
2026-08-21 13:49   ` Mukesh Pilaniya
2026-09-02  5:33 ` [PATCH v3 0/2] kexec: fix probe error codes and error propagation Mike Rapoport
2026-09-02  5:33   ` Mike Rapoport
2026-11-01 22:15 ` patchwork-bot+linux-riscv [this message]
2026-11-01 22:15   ` patchwork-bot+linux-riscv

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=179357135454.2624073.2428991164390583415.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=baoquan.he@linux.dev \
    --cc=catalin.marinas@arm.com \
    --cc=chenhuacai@kernel.org \
    --cc=include@grrlz.net \
    --cc=kernel@xen0n.name \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=loongarch@lists.linux.dev \
    --cc=ltao@redhat.com \
    --cc=mark.rutland@arm.com \
    --cc=mpilaniy@redhat.com \
    --cc=palmer@dabbelt.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=pjw@kernel.org \
    --cc=pratyush@kernel.org \
    --cc=prudo@redhat.com \
    --cc=rppt@kernel.org \
    --cc=will@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.