From: patchwork-bot+linux-riscv@kernel.org
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-riscv@lists.infradead.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-csky@vger.kernel.org,
linux-parisc@vger.kernel.org, linux-s390@vger.kernel.org,
linux-um@lists.infradead.org, loongarch@lists.linux.dev,
sparclinux@vger.kernel.org, x86@kernel.org, svens@linux.ibm.com,
nicolas@fjasle.eu, guoren@kernel.org, deller@gmx.de
Subject: Re: [PATCH v2 1/2] kbuild: unify vdso_install rules
Date: Sun, 12 Nov 2023 00:55:46 +0000 [thread overview]
Message-ID: <169975054642.11360.1289704479646976676.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231014105436.2119702-1-masahiroy@kernel.org>
Hello:
This series was applied to riscv/linux.git (fixes)
by Masahiro Yamada <masahiroy@kernel.org>:
On Sat, 14 Oct 2023 19:54:35 +0900 you wrote:
> Currently, there is no standard implementation for vdso_install,
> leading to various issues:
>
> 1. Code duplication
>
> Many architectures duplicate similar code just for copying files
> to the install destination.
>
> [...]
Here is the summary with links:
- [v2,1/2] kbuild: unify vdso_install rules
https://git.kernel.org/riscv/c/56769ba4b297
- [v2,2/2] kbuild: unify no-compiler-targets and no-sync-config-targets
https://git.kernel.org/riscv/c/9d361173edc4
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-11-12 0:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 10:54 [PATCH v2 1/2] kbuild: unify vdso_install rules Masahiro Yamada
2023-10-14 10:54 ` [PATCH v2 2/2] kbuild: unify no-compiler-targets and no-sync-config-targets Masahiro Yamada
2023-10-17 11:57 ` Nicolas Schier
2023-11-12 0:55 ` 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=169975054642.11360.1289704479646976676.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=deller@gmx.de \
--cc=guoren@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=loongarch@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=sparclinux@vger.kernel.org \
--cc=svens@linux.ibm.com \
--cc=x86@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).