From: Paul Walmsley <pjw@kernel.org>
To: Chen Pei <cp0613@linux.alibaba.com>
Cc: pjw@kernel.org, alex@ghiti.fr, debug@rivosinc.com,
guoren@kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] riscv: vdso_cfi build cleanup improvements
Date: Fri, 3 Apr 2026 02:10:00 -0600 (MDT) [thread overview]
Message-ID: <ce4db969-2b89-11da-5932-12b4765b02d6@kernel.org> (raw)
In-Reply-To: <20260320021850.1877-1-cp0613@linux.alibaba.com>
On Fri, 20 Mar 2026, cp0613@linux.alibaba.com wrote:
> From: Chen Pei <cp0613@linux.alibaba.com>
>
> This patch series addresses two issues with the RISC-V VDSO CFI build:
>
> 1. Build artifacts were not cleaned properly during 'make clean'
> 2. Copied source files were being tracked by git
>
> The first patch adds the clean-files variable to ensure that temporary
> source files copied from the main vdso directory are removed during
> make clean.
>
> The second patch adds a .gitignore file to prevent git from tracking
> build artifacts and copied source files in the vdso_cfi build directory.
>
> These changes improve the build system hygiene and maintain clean
> working directories for developers working with CFI support.
Thanks, queued for v7.1.
- Paul
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-04-03 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 2:18 [PATCH 0/2] riscv: vdso_cfi build cleanup improvements cp0613
2026-03-20 2:18 ` [PATCH 1/2] riscv: vdso_cfi: Add clean rule for copied sources cp0613
2026-03-20 2:18 ` [PATCH 2/2] riscv: vdso_cfi: Add .gitignore for build artifacts cp0613
2026-04-03 8:10 ` Paul Walmsley [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=ce4db969-2b89-11da-5932-12b4765b02d6@kernel.org \
--to=pjw@kernel.org \
--cc=alex@ghiti.fr \
--cc=cp0613@linux.alibaba.com \
--cc=debug@rivosinc.com \
--cc=guoren@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.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