From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Wei Gao" <wegao@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v11 0/2] open16: allow restricted O_CREAT of FIFOs and regular files
Date: Tue, 21 Jul 2026 08:22:59 +0000 [thread overview]
Message-ID: <6a5f2c65.3fefe569.30a19c.9c0a@mx.google.com> (raw)
In-Reply-To: <20260721074146.2779-1-wegao@suse.com>
Hi Wei,
can you please send the patch-set in a new thread, instead of replying
to the old version? we are having a really long thread in the lore
instance and it's getting diffciult to read.
https://lore.kernel.org/ltp/20250516151028.1254207-1-wegao@suse.com/
Thanks,
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-07-21 8:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <https://patchwork.ozlabs.org/project/ltp/patch/20260707022959.24088-2-wegao@suse.com/>
2026-07-07 5:47 ` [LTP] [PATCH v10 0/2] open16: allow restricted O_CREAT of FIFOs and regular files Wei Gao via ltp
2026-07-07 5:47 ` [LTP] [PATCH v10 1/2] lib: New library function tst_get_free_uid Wei Gao via ltp
2026-07-07 7:48 ` [LTP] " linuxtestproject.agent
2026-07-21 7:41 ` [LTP] [PATCH v11 0/2] open16: allow restricted O_CREAT of FIFOs and regular files Wei Gao via ltp
2026-07-21 7:41 ` [LTP] [PATCH v11 1/2] lib: New library function tst_get_free_uid Wei Gao via ltp
2026-07-21 8:38 ` [LTP] " linuxtestproject.agent
2026-07-21 7:41 ` [LTP] [PATCH v11 2/2] open16: allow restricted O_CREAT of FIFOs and regular files Wei Gao via ltp
2026-07-21 8:22 ` Andrea Cervesato via ltp [this message]
2026-07-21 8:55 ` [LTP] [PATCH v11 0/2] " Wei Gao via ltp
2026-07-07 5:47 ` [LTP] [PATCH v10 2/2] " Wei Gao via ltp
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=6a5f2c65.3fefe569.30a19c.9c0a@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=wegao@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.