From: Nam Cao <namcao@linutronix.de>
To: Gabriele Monaco <gmonaco@redhat.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Wander Lairson Costa <wander@redhat.com>,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 09/13] verification/rvgen: Delete __parse_constraint()
Date: Tue, 21 Jul 2026 16:12:56 +0200 [thread overview]
Message-ID: <877bmoxwgn.fsf@yellow.woof> (raw)
In-Reply-To: <2b19681b46b6bb5b64f1686c1ffa642a7bcef2a0.camel@redhat.com>
Gabriele Monaco <gmonaco@redhat.com> writes:
> Right good point, this is the branch I'm going to use to to send a pull request
> to Steve:
>
> https://web.git.kernel.org/pub/scm/linux/kernel/git/gmonaco/linux.git/commit/?h=for-steve
Nice!
> I don't have direct access to linux-next and I was planning to wait for my
> testing series to avoid sending Steve 2 pull requests in about a week. Unless
> there's something terribly wrong in that series, I think it's not going to take
> too long until they all land on next.
>
> What do you think?
I didn't know you can't include your tree in linux-next. That would be
nice. But well, it is still fine as is.
Nam
next prev parent reply other threads:[~2026-07-21 14:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 5:52 [PATCH v4 00/13] rv: Convert rvgen to Lark Nam Cao
2026-06-19 5:52 ` [PATCH v4 01/13] verification/rvgen: Switch LTL parser " Nam Cao
2026-06-19 5:52 ` [PATCH v4 02/13] verification/rvgen: Introduce a parse tree for automata using Lark Nam Cao
2026-06-19 5:52 ` [PATCH v4 03/13] verification/rvgen: Implement state and transition parser based on Lark Nam Cao
2026-06-19 5:52 ` [PATCH v4 04/13] verification/rvgen: Convert __fill_verify_invariants_func() to Lark Nam Cao
2026-06-19 5:52 ` [PATCH v4 05/13] verification/rvgen: Convert __fill_setup_invariants_func() " Nam Cao
2026-06-19 5:52 ` [PATCH v4 06/13] verification/rvgen: Convert __fill_verify_guards_func() " Nam Cao
2026-06-19 5:52 ` [PATCH v4 07/13] rv: Simplify hybrid automata monitors's clock variables Nam Cao
2026-06-19 5:52 ` [PATCH v4 08/13] verification/rvgen: Simplify the generation for " Nam Cao
2026-06-19 5:52 ` [PATCH v4 09/13] verification/rvgen: Delete __parse_constraint() Nam Cao
2026-06-25 8:21 ` Gabriele Monaco
2026-07-20 11:44 ` Nam Cao
2026-07-20 12:13 ` Gabriele Monaco
2026-07-21 14:12 ` Nam Cao [this message]
2026-06-19 5:52 ` [PATCH v4 10/13] verification/rvgen: Switch __get_event_variables() to Lark Nam Cao
2026-06-19 5:52 ` [PATCH v4 11/13] verification/rvgen: Switch __create_matrix() " Nam Cao
2026-06-19 5:52 ` [PATCH v4 12/13] verification/rvgen: Remove the old state variables Nam Cao
2026-06-19 5:52 ` [PATCH v4 13/13] verification/rvgen: Remove dead code Nam Cao
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=877bmoxwgn.fsf@yellow.woof \
--to=namcao@linutronix.de \
--cc=gmonaco@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=wander@redhat.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