From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 2/2] macros: Add basic docs
Date: Mon, 9 Jun 2025 09:17:03 +0200 [thread overview]
Message-ID: <20250609071703.GB1409079@pevik> (raw)
In-Reply-To: <4653486.LvFx2qVVIh@thinkpad>
Hi Cyril, all,
@Cyril: gently ping, please.
I haven't merged the patch as you express the wish to cleanup the patch.
Any concrete improvements please?
Kind regards,
Petr
https://patchwork.ozlabs.org/project/ltp/patch/20250109132334.212281-2-pvorel@suse.cz/
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-06-09 7:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 13:23 [LTP] [PATCH 1/2] [RFC] macros: Remove TEST_VOID() Petr Vorel
2025-01-09 13:23 ` [LTP] [PATCH 2/2] macros: Add basic docs Petr Vorel
2025-01-09 13:35 ` Andrea Cervesato via ltp
2025-01-10 14:57 ` Petr Vorel
2025-01-14 14:44 ` Andrea Cervesato via ltp
2025-05-09 7:00 ` Li Wang via ltp
2025-05-12 9:17 ` Avinesh Kumar
2025-06-09 7:17 ` Petr Vorel [this message]
2025-01-14 14:46 ` [LTP] [PATCH 1/2] [RFC] macros: Remove TEST_VOID() Andrea Cervesato via ltp
2025-01-14 16:20 ` Petr Vorel
2025-05-09 6:46 ` Li Wang via ltp
2025-06-09 7:14 ` Petr Vorel
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=20250609071703.GB1409079@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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