public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: cp0613@linux.alibaba.com
To: pjw@kernel.org, alex@ghiti.fr, debug@rivosinc.com, guoren@kernel.org
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	Chen Pei <cp0613@linux.alibaba.com>
Subject: [PATCH 0/2] riscv: vdso_cfi build cleanup improvements
Date: Fri, 20 Mar 2026 10:18:48 +0800	[thread overview]
Message-ID: <20260320021850.1877-1-cp0613@linux.alibaba.com> (raw)

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.

Chen Pei (2):
  riscv: vdso_cfi: Add clean rule for copied sources
  riscv: vdso_cfi: Add .gitignore for build artifacts

 arch/riscv/kernel/vdso_cfi/.gitignore | 8 ++++++++
 arch/riscv/kernel/vdso_cfi/Makefile   | 3 +++
 2 files changed, 11 insertions(+)
 create mode 100644 arch/riscv/kernel/vdso_cfi/.gitignore

-- 
2.50.1


             reply	other threads:[~2026-03-20  2:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20  2:18 cp0613 [this message]
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

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=20260320021850.1877-1-cp0613@linux.alibaba.com \
    --to=cp0613@linux.alibaba.com \
    --cc=alex@ghiti.fr \
    --cc=debug@rivosinc.com \
    --cc=guoren@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=pjw@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