From: patchwork-bot+linux-riscv@kernel.org
To: Dave Martin <Dave.Martin@arm.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, hpa@zytor.com,
James.Bottomley@HansenPartnership.com, akihiko.odaki@daynix.com,
aou@eecs.berkeley.edu, agordeev@linux.ibm.com, alex@ghiti.fr,
andreas@gaisler.com, anton.ivanov@cambridgegreys.com,
bp@alien8.de, bcain@kernel.org, catalin.marinas@arm.com,
chris@zankel.net, borntraeger@linux.ibm.com,
christophe.leroy@csgroup.eu, dave.hansen@linux.intel.com,
dinguyen@kernel.org, geert@linux-m68k.org, guoren@kernel.org,
hca@linux.ibm.com, deller@gmx.de, chenhuacai@kernel.org,
mingo@redhat.com, johannes@sipsolutions.net,
glaubitz@physik.fu-berlin.de, jonas@southpole.se,
kees@kernel.org, maddy@linux.ibm.com, jcmvbkbc@gmail.com,
mpe@ellerman.id.au, npiggin@gmail.com, oleg@redhat.com,
palmer@dabbelt.com, paul.walmsley@sifive.com, dalias@libc.org,
richard@nod.at, linux@armlinux.org.uk, shorne@gmail.com,
stefan.kristiansson@saunalahti.fi, svens@linux.ibm.com,
tsbogend@alpha.franken.de, tglx@linutronix.de, gor@linux.ibm.com,
vgupta@kernel.org, kernel@xen0n.name, will@kernel.org,
ysato@users.sourceforge.jp, linux-arch@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-csky@vger.kernel.org,
linux-hexagon@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
linux-mips@vger.kernel.org, linux-openrisc@vger.kernel.org,
linux-parisc@vger.kernel.org, linux-s390@vger.kernel.org,
linux-sh@vger.kernel.org, linux-snps-arc@lists.infradead.org,
linux-um@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
loongarch@lists.linux.dev, sparclinux@vger.kernel.org,
x86@kernel.org
Subject: Re: [PATCH 00/23] binfmt_elf,arch/*: Use elf.h for coredump note names
Date: Sun, 10 Aug 2025 21:12:43 +0000 [thread overview]
Message-ID: <175486036374.1221929.319441619761028585.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250701135616.29630-1-Dave.Martin@arm.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Kees Cook <kees@kernel.org>:
On Tue, 1 Jul 2025 14:55:53 +0100 you wrote:
> This series aims to clean up an aspect of coredump generation:
>
> ELF coredumps contain a set of notes describing the state of machine
> registers and other information about the dumped process.
>
> Notes are identified by a numeric identifier n_type and a "name"
> string, although this terminology is somewhat misleading. Officially,
> the "name" of a note is really an "originator" or namespace identifier
> that indicates how to interpret n_type [1], although in practice it is
> often used more loosely.
>
> [...]
Here is the summary with links:
- [16/23] riscv: ptrace: Use USER_REGSET_NOTE_TYPE() to specify regset note names
https://git.kernel.org/riscv/c/c9502cc7bef5
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: Dave Martin <Dave.Martin@arm.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, hpa@zytor.com,
James.Bottomley@HansenPartnership.com, akihiko.odaki@daynix.com,
aou@eecs.berkeley.edu, agordeev@linux.ibm.com, alex@ghiti.fr,
andreas@gaisler.com, anton.ivanov@cambridgegreys.com,
bp@alien8.de, bcain@kernel.org, catalin.marinas@arm.com,
chris@zankel.net, borntraeger@linux.ibm.com,
christophe.leroy@csgroup.eu, dave.hansen@linux.intel.com,
dinguyen@kernel.org, geert@linux-m68k.org, guoren@kernel.org,
hca@linux.ibm.com, deller@gmx.de, chenhuacai@kernel.org,
mingo@redhat.com, johannes@sipsolutions.net,
glaubitz@physik.fu-berlin.de, jonas@southpole.se,
kees@kernel.org, maddy@linux.ibm.com, jcmvbkbc@gmail.com,
mpe@ellerman.id.au, npiggin@gmail.com, oleg@redhat.com,
palmer@dabbelt.com, paul.walmsley@sifive.com, dalias@libc.org,
richard@nod.at, linux@armlinux.org.uk, shorne@gmail.com,
stefan.kristiansson@saunalahti.fi, svens@linux.ibm.com,
tsbogend@alpha.franken.de, tglx@linutronix.de, gor@linux.ibm.com,
vgupta@kernel.org, kernel@xen0n.name, will@kernel.org,
ysato@users.sourceforge.jp, linux-arch@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-csky@vger.kernel.org,
linux-hexagon@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
linux-mips@vger.kernel.org, linux-openrisc@vger.kernel.org,
linux-parisc@vger.kernel.org, linux-s390@vger.kernel.org,
linux-sh@vger.kernel.org, linux-snps-arc@lists.infradead.org,
linux-um@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
loongarch@lists.linux.dev, sparclinux@vger.kernel.org,
x86@kernel.org
Subject: Re: [PATCH 00/23] binfmt_elf,arch/*: Use elf.h for coredump note names
Date: Sun, 10 Aug 2025 21:12:43 +0000 [thread overview]
Message-ID: <175486036374.1221929.319441619761028585.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250701135616.29630-1-Dave.Martin@arm.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Kees Cook <kees@kernel.org>:
On Tue, 1 Jul 2025 14:55:53 +0100 you wrote:
> This series aims to clean up an aspect of coredump generation:
>
> ELF coredumps contain a set of notes describing the state of machine
> registers and other information about the dumped process.
>
> Notes are identified by a numeric identifier n_type and a "name"
> string, although this terminology is somewhat misleading. Officially,
> the "name" of a note is really an "originator" or namespace identifier
> that indicates how to interpret n_type [1], although in practice it is
> often used more loosely.
>
> [...]
Here is the summary with links:
- [16/23] riscv: ptrace: Use USER_REGSET_NOTE_TYPE() to specify regset note names
https://git.kernel.org/riscv/c/c9502cc7bef5
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
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Dave Martin <Dave.Martin@arm.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, hpa@zytor.com,
James.Bottomley@HansenPartnership.com, akihiko.odaki@daynix.com,
aou@eecs.berkeley.edu, agordeev@linux.ibm.com, alex@ghiti.fr,
andreas@gaisler.com, anton.ivanov@cambridgegreys.com,
bp@alien8.de, bcain@kernel.org, catalin.marinas@arm.com,
chris@zankel.net, borntraeger@linux.ibm.com,
christophe.leroy@csgroup.eu, dave.hansen@linux.intel.com,
dinguyen@kernel.org, geert@linux-m68k.org, guoren@kernel.org,
hca@linux.ibm.com, deller@gmx.de, chenhuacai@kernel.org,
mingo@redhat.com, johannes@sipsolutions.net,
glaubitz@physik.fu-berlin.de, jonas@southpole.se,
kees@kernel.org, maddy@linux.ibm.com, jcmvbkbc@gmail.com,
mpe@ellerman.id.au, npiggin@gmail.com, oleg@redhat.com,
palmer@dabbelt.com, paul.walmsley@sifive.com, dalias@libc.org,
richard@nod.at, linux@armlinux.org.uk, shorne@gmail.com,
stefan.kristiansson@saunalahti.fi, svens@linux.ibm.com,
tsbogend@alpha.franken.de, tglx@linutronix.de, gor@linux.ibm.com,
vgupta@kernel.org, kernel@xen0n.name, will@kernel.org,
ysato@users.sourceforge.jp, linux-arch@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-csky@vger.kernel.org,
linux-hexagon@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
linux-mips@vger.kernel.org, linux-openrisc@vger.kernel.org,
linux-parisc@vger.kernel.org, linux-s390@vger.kernel.org,
linux-sh@vger.kernel.org, linux-snps-arc@lists.infradead.org,
linux-um@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
loongarch@lists.linux.dev, sparclinux@vger.kernel.org,
x86@kernel.org
Subject: Re: [PATCH 00/23] binfmt_elf,arch/*: Use elf.h for coredump note names
Date: Sun, 10 Aug 2025 21:12:43 +0000 [thread overview]
Message-ID: <175486036374.1221929.319441619761028585.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250701135616.29630-1-Dave.Martin@arm.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Kees Cook <kees@kernel.org>:
On Tue, 1 Jul 2025 14:55:53 +0100 you wrote:
> This series aims to clean up an aspect of coredump generation:
>
> ELF coredumps contain a set of notes describing the state of machine
> registers and other information about the dumped process.
>
> Notes are identified by a numeric identifier n_type and a "name"
> string, although this terminology is somewhat misleading. Officially,
> the "name" of a note is really an "originator" or namespace identifier
> that indicates how to interpret n_type [1], although in practice it is
> often used more loosely.
>
> [...]
Here is the summary with links:
- [16/23] riscv: ptrace: Use USER_REGSET_NOTE_TYPE() to specify regset note names
https://git.kernel.org/riscv/c/c9502cc7bef5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
next prev parent reply other threads:[~2025-08-10 21:12 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 13:55 [PATCH 00/23] binfmt_elf,arch/*: Use elf.h for coredump note names Dave Martin
2025-07-01 13:55 ` Dave Martin
2025-07-01 13:55 ` Dave Martin
2025-07-01 13:55 ` [PATCH 01/23] regset: Fix kerneldoc for struct regset_get() in user_regset Dave Martin
2025-07-01 13:55 ` [PATCH 02/23] regset: Add explicit core note name in struct user_regset Dave Martin
2025-07-09 11:57 ` Alexander Gordeev
2025-07-01 13:55 ` [PATCH 03/23] binfmt_elf: Dump non-arch notes with strictly matching name and type Dave Martin
2025-07-01 13:55 ` [PATCH 04/23] ARC: ptrace: Use USER_REGSET_NOTE_TYPE() to specify regset note names Dave Martin
2025-07-01 13:55 ` Dave Martin
2025-07-01 13:55 ` [PATCH 05/23] ARM: " Dave Martin
2025-07-01 13:55 ` [PATCH 06/23] arm64: " Dave Martin
2025-07-01 13:56 ` [PATCH 07/23] csky: " Dave Martin
2025-07-01 13:56 ` [PATCH 08/23] hexagon: " Dave Martin
2025-07-01 13:56 ` [PATCH 09/23] LoongArch: " Dave Martin
2025-07-01 13:56 ` [PATCH 10/23] m68k: " Dave Martin
2025-07-06 9:25 ` Geert Uytterhoeven
2025-07-07 10:54 ` Dave Martin
2025-07-01 13:56 ` [PATCH 11/23] MIPS: " Dave Martin
2025-07-01 13:56 ` [PATCH 12/23] nios2: " Dave Martin
2025-07-01 13:56 ` [PATCH 13/23] openrisc: " Dave Martin
2025-07-01 13:56 ` [PATCH 14/23] parisc: " Dave Martin
2025-07-01 13:56 ` [PATCH 15/23] powerpc/ptrace: " Dave Martin
2025-07-01 13:56 ` [PATCH 16/23] riscv: ptrace: " Dave Martin
2025-07-01 13:56 ` Dave Martin
2025-07-01 13:56 ` [PATCH 17/23] s390/ptrace: " Dave Martin
2025-07-09 11:58 ` Alexander Gordeev
2025-07-01 13:56 ` [PATCH 18/23] sh: ptrace: " Dave Martin
2025-07-01 13:56 ` [PATCH 19/23] sparc: " Dave Martin
2025-07-01 13:56 ` [PATCH 20/23] x86/ptrace: " Dave Martin
2025-07-01 13:56 ` [PATCH 21/23] um: ptrace: " Dave Martin
2025-07-04 11:58 ` Johannes Berg
2025-07-04 16:46 ` Dave Martin
2025-07-01 13:56 ` [PATCH 22/23] xtensa: " Dave Martin
2025-07-01 13:56 ` [PATCH 23/23] binfmt_elf: Warn on missing or suspicious " Dave Martin
2025-07-05 15:14 ` Kees Cook
2025-07-07 11:03 ` Dave Martin
2025-07-09 5:05 ` [PATCH 00/23] binfmt_elf,arch/*: Use elf.h for coredump " Akihiko Odaki
2025-07-09 5:05 ` Akihiko Odaki
2025-07-09 5:05 ` Akihiko Odaki
2025-07-15 5:37 ` Kees Cook
2025-07-15 5:37 ` Kees Cook
2025-07-15 5:37 ` Kees Cook
2025-07-15 10:32 ` Dave Martin
2025-07-15 10:32 ` Dave Martin
2025-07-15 10:32 ` Dave Martin
2025-08-10 21:12 ` patchwork-bot+linux-riscv [this message]
2025-08-10 21:12 ` patchwork-bot+linux-riscv
2025-08-10 21:12 ` 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=175486036374.1221929.319441619761028585.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=Dave.Martin@arm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=agordeev@linux.ibm.com \
--cc=akihiko.odaki@daynix.com \
--cc=alex@ghiti.fr \
--cc=andreas@gaisler.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=aou@eecs.berkeley.edu \
--cc=bcain@kernel.org \
--cc=borntraeger@linux.ibm.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=chris@zankel.net \
--cc=christophe.leroy@csgroup.eu \
--cc=dalias@libc.org \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=dinguyen@kernel.org \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=gor@linux.ibm.com \
--cc=guoren@kernel.org \
--cc=hca@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=jcmvbkbc@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=jonas@southpole.se \
--cc=kees@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-openrisc@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=linux-um@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=loongarch@lists.linux.dev \
--cc=maddy@linux.ibm.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=oleg@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=richard@nod.at \
--cc=shorne@gmail.com \
--cc=sparclinux@vger.kernel.org \
--cc=stefan.kristiansson@saunalahti.fi \
--cc=svens@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.de \
--cc=vgupta@kernel.org \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=ysato@users.sourceforge.jp \
/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.