lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <171316879419.200641.10651479011126419872.b4-ty@kernel.org>
Date: Mon, 15 Apr 2024 10:13:14 +0200
From: Maxime Ripard <mripard@...nel.org>
To: dri-devel@...ts.freedesktop.org, 
 Sebastian Wick <sebastian.wick@...hat.com>
Cc: David Airlie <airlied@...il.com>, Daniel Vetter <daniel@...ll.ch>, 
 Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>, 
 Thomas Zimmermann <tzimmermann@...e.de>, Jonathan Corbet <corbet@....net>, 
 linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Daniel Vetter <daniel.vetter@...ll.ch>
Subject: Re: (subset) [PATCH v2] drm: Document requirements for
 driver-specific KMS props in new drivers

On Wed, 10 Apr 2024 14:20:06 +0200, Sebastian Wick wrote:
> When extending support for a driver-specific KMS property to additional
> drivers, we should apply all the requirements for new properties and
> make sure the semantics are the same and documented.
> 
> v2: devs of the driver which introduced property shall help and ack
> 
> 
> [...]

Applied to misc/kernel.git (drm-misc-next).

Thanks!
Maxime


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ