From: Chris Li <sparse@chrisli.org>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>, changyuan.lv@gmail.com
Subject: Sparse merge window is open
Date: Sat, 27 Sep 2025 21:45:16 -0700 [thread overview]
Message-ID: <CACePvbUajv=xC0J4eKdVoskRvKQDwxrM4v17+6t1M42xsbQ-gg@mail.gmail.com> (raw)
Hi everyone,
After a long break from sparse the project. I have fully returned back
to resume the maintainer role on sparse. I want to thank Luc for
taking great care of the project while I am gone. Looking forward to
the pull request from him again.
I am going through the mailing list for old patches that can be
applied to sparse but I haven't found much yet.
If you have patches that can be applied to sparse, now is a good time
to re-submit them. I want to cut a release after this round of merge
window.
Regarding the sparse vs sparse-dev repo. Here is how I intend to use
these two repo:
1) sparse repo. This is the stable repo, the git history will not
rewind. If something bad happens to the old commit, a revert commit
will be added to remove the problematic commit.
2) sparse-dev repo. This repo is always using sparse stable repo as
base. However the change newer than the sparse stable repo is not
guaranteed to be stable. I might rewind and re-apply a newer version
of the patches. Consider it as a staging repo. I will merge (fast
forward) from the sparse-dev to sparse at about weekly or bi-weekly
bases. Testing please use the sparse-dev repo for the cutting edge
changes.
If you want to submit patches to sparse, recommend using the stable
sparse repo as the base. Only use sparse-dev as base if there are very
bleeding edge patches that only exist on sparse-dev.
Pull request please use the sparse repo as well.
Another issue I want to collect some feedback is that, the kernel has
remove the sparse context checker:
https://lore.kernel.org/linux-sparse/20250918140451.1289454-23-elver@google.com/
Does any once feel strongly removing the lock context code in sparse
itself because the main usage case is now gone?
Chris
reply other threads:[~2025-09-28 4:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CACePvbUajv=xC0J4eKdVoskRvKQDwxrM4v17+6t1M42xsbQ-gg@mail.gmail.com' \
--to=sparse@chrisli.org \
--cc=changyuan.lv@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).