From: patchwork-bot+linux-riscv@kernel.org
To: liaochang (A) <liaochang1@huawei.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
heiko.stuebner@vrull.eu, ajones@ventanamicro.com,
prabhakar.mahadev-lad.rj@bp.renesas.com,
conor.dooley@microchip.com, jszhang@kernel.org,
vincent.chen@sifive.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: Add header include guards to insn.h
Date: Wed, 22 Feb 2023 15:00:22 +0000 [thread overview]
Message-ID: <167707802217.24438.17901281821213780885.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230129094242.282620-1-liaochang1@huawei.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Sun, 29 Jan 2023 17:42:42 +0800 you wrote:
> Add header include guards to insn.h to prevent repeating declaration of
> any identifiers in insn.h.
>
> Fixes: edde5584c7ab ("riscv: Add SW single-step support for KDB")
> Signed-off-by: Liao Chang <liaochang1@huawei.com>
> ---
> arch/riscv/include/asm/insn.h | 4 ++++
> 1 file changed, 4 insertions(+)
Here is the summary with links:
- riscv: Add header include guards to insn.h
https://git.kernel.org/riscv/c/8ac6e619d9d5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-02-22 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 9:42 [PATCH] riscv: Add header include guards to insn.h Liao Chang
2023-01-30 7:35 ` Andrew Jones
2023-01-30 14:53 ` Conor Dooley
2023-02-01 9:37 ` liaochang (A)
2023-02-01 9:42 ` Conor Dooley
2023-02-02 0:52 ` liaochang (A)
2023-02-02 3:33 ` Joe Perches
2023-02-02 11:36 ` liaochang (A)
2023-02-22 15:00 ` 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=167707802217.24438.17901281821213780885.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=heiko.stuebner@vrull.eu \
--cc=jszhang@kernel.org \
--cc=liaochang1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=vincent.chen@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