From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] sched_rr_get_interval01: Add another kernel tag
Date: Fri, 1 Sep 2023 11:41:45 +0200 [thread overview]
Message-ID: <ZPGx2VbtreROQC2N@yuki> (raw)
In-Reply-To: <20230818071323.89606-1-pvorel@suse.cz>
Hi!
> NOTE: git commit is still only in next tree [1], although hash will be
> very likely the same, we should wait until it get to mainline (likely in
> 6.6-rc1).
The fix has reached the mainline with unchanged hash hence patch
applied, thanks.
> I suppose we could write a test for another Cyril's fix [2].
I guess that I can just send patch for that one, should be fairly easy.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-09-01 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 7:13 [LTP] [PATCH 1/1] sched_rr_get_interval01: Add another kernel tag Petr Vorel
2023-09-01 9:41 ` Cyril Hrubis [this message]
2023-09-01 10:45 ` 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=ZPGx2VbtreROQC2N@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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