All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: Sebastian Chlad <schlad@suse.de>,
	ltp@lists.linux.it, Martin Doucha <martin.doucha@suse.com>
Subject: Re: [LTP] LTP old API conversion
Date: Tue, 17 Mar 2026 23:39:20 +0100	[thread overview]
Message-ID: <20260317223920.GA370623@pevik> (raw)
In-Reply-To: <69b945ab.050a0220.1eaaec.d93b@mx.google.com>

> Hi Petr,

> > I'd vote for limiting patchsets to max tests in a single directory.
> > Why? Smaller patchset is easier to review. And if just some of the commits are
> > accepted then fewer commits need to be rebased.

> Do you mean one patch-set for multiple (unrelated) tests (for instance syscalls
> folder) [1], or one patch-set per testing suite [2] ?

I meant [2], i.e. tests from certain folder (usually tests related to single syscall).
But it's just a suggestion, feel free to do it differently if it's significantly
simpler.

Thanks for this effort.

Kind regards,
Petr

> [1] would be 20 random tests from testcases/kerne/syscalls
> [2] i.e. all tests to refactor in `testcases/kernel/mem/mmapstress`

> I would follow the first approach if we want to send a big amount of patches,
> or the second if we want to be more specific.

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-03-17 22:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 10:42 [LTP] LTP old API conversion Andrea Cervesato via ltp
2026-03-17 11:58 ` Petr Vorel
2026-03-17 12:14   ` Andrea Cervesato via ltp
2026-03-17 22:39     ` Petr Vorel [this message]
2026-03-18  5:36       ` Li Wang via ltp
2026-03-17 15:32 ` Cyril Hrubis
2026-03-17 15:49   ` Andrea Cervesato via ltp
2026-03-18 13:04     ` Andrea Cervesato via ltp
2026-03-18  5:18   ` Li Wang 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=20260317223920.GA370623@pevik \
    --to=pvorel@suse.cz \
    --cc=andrea.cervesato@suse.com \
    --cc=ltp@lists.linux.it \
    --cc=martin.doucha@suse.com \
    --cc=schlad@suse.de \
    /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.