Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <mripard@kernel.org>
To: igt-dev@lists.freedesktop.org,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: "Maxime Ripard" <mripard@kernel.org>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Subject: Re: [PATCH i-g-t RESEND v3 0/2] tests/kms_properties: rework immutability checks
Date: Fri,  6 Dec 2024 08:24:25 +0100	[thread overview]
Message-ID: <173346986166.831483.14698392158753288549.b4-ty@kernel.org> (raw)
In-Reply-To: <20241115-rework-imm-check-v3-0-e4077cf16816@linaro.org>

On Fri, 15 Nov 2024 23:18:57 +0200, Dmitry Baryshkov wrote:
> Following the discussion on IRC, it is actually an error to require that
> properties that can not be chaged are marked as immutable.
> 
> The DRM_MODE_PROP_IMMUTABLE defines more of the 'direction' of the
> property (whether it is set by the kernel or it is expected to be set by
> the userspace) rather than simply states that there is no way for the
> userspace to change the property.
> 
> [...]

Applied to git@gitlab.freedesktop.org:drm/igt-gpu-tools.git (master).

Thanks!
Maxime

      parent reply	other threads:[~2024-12-06  7:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-15 21:18 [PATCH i-g-t RESEND v3 0/2] tests/kms_properties: rework immutability checks Dmitry Baryshkov
2024-11-15 21:18 ` [PATCH i-g-t RESEND v3 1/2] tests/kms_properties: drop " Dmitry Baryshkov
2024-11-15 21:18 ` [PATCH i-g-t RESEND v3 2/2] tests/kms_properties: add sanity checks for properties Dmitry Baryshkov
2024-11-15 22:00 ` ✓ CI.xeBAT: success for tests/kms_properties: rework immutability checks (rev4) Patchwork
2024-11-15 23:27 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-11-16  3:24 ` ✗ CI.xeFULL: " Patchwork
2024-11-22 12:34 ` [PATCH i-g-t RESEND v3 0/2] tests/kms_properties: rework immutability checks Dmitry Baryshkov
2024-12-06  7:24 ` Maxime Ripard [this message]

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=173346986166.831483.14698392158753288549.b4-ty@kernel.org \
    --to=mripard@kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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