From: "Laguna, Lukasz" <lukasz.laguna@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
<igt-dev@lists.freedesktop.org>,
<marcin.bernatowicz@linux.intel.com>,
<zbigniew.kempczynski@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 1/1] lib/igt_core: initialize srandom seed on startup
Date: Fri, 24 Nov 2023 10:04:41 +0100 [thread overview]
Message-ID: <dfc1e93d-6d75-4b61-b04a-9e3f361609ed@intel.com> (raw)
In-Reply-To: <20231123173520.vrgapopkcmmmbqnb@kamilkon-desk.igk.intel.com>
On 11/23/2023 18:35, Kamil Konieczny wrote:
> Hi Lukasz,
> On 2023-11-22 at 13:40:52 +0100, Lukasz Laguna wrote:
>> Init seed for random number generator on IGT startup.
>>
>> Signed-off-by: Lukasz Laguna <lukasz.laguna@intel.com>
> LGTM
> Reviewed-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Hi Kamil,
Thanks for review. I've just sent a patch with rb added. Can you please
merge it?
>> ---
>> lib/igt_core.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/lib/igt_core.c b/lib/igt_core.c
>> index 041e4b328..1abe3d337 100644
>> --- a/lib/igt_core.c
>> +++ b/lib/igt_core.c
>> @@ -1283,6 +1283,7 @@ out:
>> bind_fbcon(false);
>> igt_kmsg(KMSG_INFO "%s: executing\n", command_str);
>> print_version();
>> + igt_srandom();
>>
>> sync();
>> oom_adjust_for_doom();
>> --
>> 2.40.0
>>
next prev parent reply other threads:[~2023-11-24 9:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 12:40 [igt-dev] [PATCH i-g-t 0/1] lib/igt_core: initialize srandom seed on startup Lukasz Laguna
2023-11-22 12:40 ` [igt-dev] [PATCH i-g-t 1/1] " Lukasz Laguna
2023-11-23 17:35 ` Kamil Konieczny
2023-11-24 9:04 ` Laguna, Lukasz [this message]
2023-11-22 16:20 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2023-11-22 17:37 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-11-24 9:03 [igt-dev] [PATCH i-g-t 0/1] " Lukasz Laguna
2023-11-24 9:03 ` [igt-dev] [PATCH i-g-t 1/1] " Lukasz Laguna
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=dfc1e93d-6d75-4b61-b04a-9e3f361609ed@intel.com \
--to=lukasz.laguna@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=marcin.bernatowicz@linux.intel.com \
--cc=zbigniew.kempczynski@intel.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