From: patchwork-bot+linux-riscv@kernel.org
To: Drew Fustini <dfustini@baylibre.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, guoren@kernel.org,
lizhengyu3@huawei.com, bjorn@rivosinc.com, heiko@sntech.de,
liaochang1@huawei.com, masahiroy@kernel.org,
alexghiti@rivosinc.com, jszhang@kernel.org, arnd@arndb.de,
linux-kernel@vger.kernel.org, conor.dooley@microchip.com,
lkp@intel.com, guoren@linux.alibaba.com
Subject: Re: [PATCH] riscv: compat_syscall_table: Fixup compile warning
Date: Mon, 08 May 2023 14:41:56 +0000 [thread overview]
Message-ID: <168355691623.25692.1628612275748085711.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230501223353.2833899-1-dfustini@baylibre.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Mon, 1 May 2023 15:33:54 -0700 you wrote:
> From: Guo Ren <guoren@linux.alibaba.com>
>
> ../arch/riscv/kernel/compat_syscall_table.c:12:41: warning: initialized
> field overwritten [-Woverride-init]
> 12 | #define __SYSCALL(nr, call) [nr] = (call),
> | ^
> ../include/uapi/asm-generic/unistd.h:567:1: note: in expansion of macro
> '__SYSCALL'
> 567 | __SYSCALL(__NR_semget, sys_semget)
>
> [...]
Here is the summary with links:
- riscv: compat_syscall_table: Fixup compile warning
https://git.kernel.org/riscv/c/f9c4bbddece7
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
prev parent reply other threads:[~2023-05-08 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 22:33 [PATCH] riscv: compat_syscall_table: Fixup compile warning Drew Fustini
2023-05-01 22:44 ` Palmer Dabbelt
2023-05-08 14:41 ` patchwork-bot+linux-riscv [this message]
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=168355691623.25692.1628612275748085711.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=bjorn@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=dfustini@baylibre.com \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=heiko@sntech.de \
--cc=jszhang@kernel.org \
--cc=liaochang1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lizhengyu3@huawei.com \
--cc=lkp@intel.com \
--cc=masahiroy@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
/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