From: Markus Theil <theil.markus@gmail.com>
To: Andi Shyti <andi.shyti@linux.intel.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org,
netdev@vger.kernel.org, tytso@mit.edu
Subject: Re: [PATCH] prandom: remove next_pseudo_random32
Date: Tue, 11 Feb 2025 07:13:41 +0100 [thread overview]
Message-ID: <619aec64-b191-49f0-99ce-2c2af9493e58@gmail.com> (raw)
In-Reply-To: <Z6qGtsEdjpz4ETvl@ashyti-mobl2.lan>
Hi,
On 11.02.25 00:07, Andi Shyti wrote:
> actually would be better if we apply the i915 part in drm-tip
> rather than waiting for kernel releases to receive this change in
> our branch. It has been source of conflicts and headaches.
>
> May I ask Markus to split the patch in two parts and we handle
> the i915 side?
>
Sure, will do in a v2.
Markus
next prev parent reply other threads:[~2025-02-12 14:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 13:35 [PATCH] prandom: remove next_pseudo_random32 Markus Theil
2025-02-10 13:39 ` Jason A. Donenfeld
2025-02-10 23:07 ` Andi Shyti
2025-02-11 6:13 ` Markus Theil [this message]
2025-02-11 6:33 ` [PATCH v2 0/3] " Markus Theil
2025-02-11 6:33 ` [PATCH v2 1/3] drm/i915/selftests: use prandom in selftest Markus Theil
2025-02-13 17:19 ` Andi Shyti
2025-03-19 17:13 ` Jason A. Donenfeld
2025-03-21 12:37 ` Jani Nikula
2025-03-21 12:52 ` Jason A. Donenfeld
2025-02-11 6:33 ` [PATCH v2 2/3] media: vivid: use prandom Markus Theil
2025-02-11 6:33 ` [PATCH v2 3/3] prandom: remove next_pseudo_random32 Markus Theil
2025-02-13 14:27 ` [PATCH v2 0/3] " Krzysztof Karas
2025-02-12 18:47 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2,1/3] drm/i915/selftests: use prandom in selftest Patchwork
2025-02-12 19:07 ` ✓ i915.CI.BAT: success " Patchwork
2025-02-13 3:29 ` ✗ i915.CI.Full: failure " Patchwork
2025-02-10 18:16 ` ✗ Fi.CI.CHECKPATCH: warning for prandom: remove next_pseudo_random32 Patchwork
2025-02-10 20:48 ` ✓ i915.CI.BAT: success " Patchwork
2025-02-11 3:26 ` ✗ i915.CI.Full: failure " Patchwork
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=619aec64-b191-49f0-99ce-2c2af9493e58@gmail.com \
--to=theil.markus@gmail.com \
--cc=Jason@zx2c4.com \
--cc=andi.shyti@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tytso@mit.edu \
/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