From: Jani Nikula <jani.nikula@linux.intel.com>
To: Sebastian Brzezinka <sebastian.brzezinka@intel.com>,
Sebastian Brzezinka <sebastian.brzezinka@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: andi.shyti@linux.intel.com, krzysztof.karas@intel.com
Subject: Re: [PATCH] drm/i915: replace fetch_and_zero() with kernel xchg()
Date: Mon, 27 Apr 2026 15:48:37 +0300 [thread overview]
Message-ID: <b7e7bf8c2f0946763f992dc06342e0bfaba98c90@intel.com> (raw)
In-Reply-To: <DI3XYF0I8YPD.336A8XEBGNCDT@intel.com>
On Mon, 27 Apr 2026, Sebastian Brzezinka <sebastian.brzezinka@intel.com> wrote:
> This patch was initially sent to trybot and received Review-by: Krzysztof
> there. So I’ve copied it here.
In most cases, patches shouldn't be sent to trybot, and the trybot list
shouldn't be used for reviews.
Trybot is primarily for testing out an idea when you're not sure how
things would work on a bunch of real hardware. Or when the patch is not
intended for merging at all. It's not for a generic preliminary round of
testing. If trybot results pass, you'll still need to send the patch for
CI and review and merging on the actual list, and it just ends up
wasting a CI round.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-04-27 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 12:13 [PATCH] drm/i915: replace fetch_and_zero() with kernel xchg() Sebastian Brzezinka
2026-04-27 12:26 ` Jani Nikula
2026-04-27 12:37 ` Sebastian Brzezinka
2026-04-27 12:48 ` Jani Nikula [this message]
2026-04-27 12:51 ` Sebastian Brzezinka
2026-04-27 12:54 ` Jani Nikula
2026-04-28 14:47 ` Andi Shyti
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=b7e7bf8c2f0946763f992dc06342e0bfaba98c90@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=krzysztof.karas@intel.com \
--cc=sebastian.brzezinka@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 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.