From: Bart Van Assche <bvanassche@acm.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Laight <david.laight.linux@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
Chris Li <sparse@chrisli.org>
Subject: Re: [PATCH v2] tracing: Make is_signed_type() compatible with sparse
Date: Tue, 1 Sep 2026 15:46:45 -0700 [thread overview]
Message-ID: <d5c64d53-1d36-43c5-9122-8a57b4bda9b0@acm.org> (raw)
In-Reply-To: <CAHk-=wj1rTtCXQVf-_doFT0KbnCDObvuoG0yEv8eH6V+Yq4=vg@mail.gmail.com>
On 9/1/26 1:24 PM, Linus Torvalds wrote:
> This is partly me fishing for some poor soul who actually *wants* to
> maintain this.
It is well known that the official repository for sparse is
git://git.kernel.org/pub/scm/devel/sparse/sparse.git so I think we
should keep that URL. Pushing changes to that repository requires a
kernel.org account. I lost my kernel.org PGP key about nine years ago so
I will have to create a new one and get it signed again. I will let you
know when my new PGP key has been signed and when Konstantin Ryabitsev
has reactivated my kernel.org account.
Thanks,
Bart.
next prev parent reply other threads:[~2026-09-01 22:46 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 17:00 Bart Van Assche
2026-08-31 0:20 ` Bart Van Assche
2026-08-31 14:27 ` Steven Rostedt
2026-08-31 20:44 ` David Laight
2026-08-31 21:19 ` Bart Van Assche
2026-09-01 8:20 ` David Laight
2026-09-01 18:05 ` Bart Van Assche
2026-09-01 18:45 ` Linus Torvalds
2026-09-01 19:22 ` Bart Van Assche
2026-09-01 19:35 ` Linus Torvalds
2026-09-01 19:38 ` Linus Torvalds
2026-09-01 20:06 ` Bart Van Assche
2026-09-01 20:24 ` Linus Torvalds
2026-09-01 22:46 ` Bart Van Assche [this message]
2026-09-05 7:48 ` Uwe Kleine-König
2026-09-01 21:29 ` David Laight
2026-09-01 21:43 ` Bart Van Assche
2026-09-01 21:56 ` Linus Torvalds
2026-09-01 23:25 ` Steven Rostedt
2026-09-02 8:24 ` David Laight
2026-09-02 13:36 ` Steven Rostedt
2026-09-02 15:16 ` David Laight
2026-09-02 16:31 ` Bart Van Assche
2026-09-02 16:39 ` Steven Rostedt
2026-09-02 16:44 ` Bart Van Assche
2026-09-02 16:54 ` Steven Rostedt
2026-09-02 17:04 ` Linus Torvalds
2026-09-02 17:24 ` Steven Rostedt
2026-09-02 18:06 ` David Laight
2026-09-02 18:21 ` Steven Rostedt
2026-09-02 20:50 ` David Laight
2026-09-02 22:40 ` Bart Van Assche
2026-09-02 22:43 ` Linus Torvalds
2026-09-02 16:52 ` Linus Torvalds
2026-09-03 21:50 ` Vincent Mailhol
2026-09-04 0:26 ` Steven Rostedt
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=d5c64d53-1d36-43c5-9122-8a57b4bda9b0@acm.org \
--to=bvanassche@acm.org \
--cc=david.laight.linux@gmail.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=luc.vanoostenryck@gmail.com \
--cc=rostedt@goodmis.org \
--cc=sparse@chrisli.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®