From: Simon Ser <contact@emersion.fr>
To: Hans de Goede <hdegoede@redhat.com>
Cc: dri-devel@lists.freedesktop.org,
Marco Trevisan <marco.trevisan@canonical.com>,
Mark Gross <mgross@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Sebastien Bacher <seb128@ubuntu.com>,
David Airlie <airlied@linux.ie>,
Mario Limonciello <mario.limonciello@outlook.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
platform-driver-x86@vger.kernel.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Pekka Paalanen <pekka.paalanen@collabora.com>,
Mark Pearson <markpearson@lenovo.com>,
Rajat Jain <rajatja@google.com>,
Andy Shevchenko <andy@infradead.org>
Subject: Re: [PATCH v2 0/9] drm: Add privacy-screen class and connector properties
Date: Thu, 22 Apr 2021 08:58:08 +0000 [thread overview]
Message-ID: <xVZdxPoOewlP5LmxWy2EHKEIxRw1oeQH9xfPG5a6i8O5IJf5AqpFelwBSIoacwhIqCWJG0sqzHpfGL3WqAxM0CZOUyCOPUuCToD8Ia1Dwjw=@emersion.fr> (raw)
In-Reply-To: <88ad0981-0763-9c8d-fb57-70278bcaffd4@redhat.com>
On Thursday, April 22nd, 2021 at 10:54 AM, Hans de Goede <hdegoede@redhat.com> wrote:
> I guess Marco was waiting for the kernel bits too land before submitting these,
> but I agree that it would probably be good to have these submitted now, we
> can mark them as WIP to avoid them getting merged before the kernel side
> is finalized.
Yes, this is how it should be done, see [1]. In particular:
> The userspace side must be fully reviewed and tested to the standards
> of that userspace project.
And yeah, the user-space side still can't be merged before the kernel
side:
> The kernel patch can only be merged after all the above requirements
> are met, but it must be merged to either drm-next or drm-misc-next
> before the userspace patches land.
[1]: https://dri.freedesktop.org/docs/drm/gpu/drm-uapi.html#open-source-userspace-requirements
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-04-22 8:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 20:47 [PATCH v2 0/9] drm: Add privacy-screen class and connector properties Hans de Goede
2021-04-21 20:47 ` [PATCH v2 1/9] drm/connector: Add support for privacy-screen properties (v4) Hans de Goede
2021-04-21 20:47 ` [PATCH v2 2/9] drm: Add privacy-screen class (v2) Hans de Goede
2021-06-01 15:31 ` [Intel-gfx] " Emil Velikov
2021-06-01 16:50 ` Marco Trevisan
2021-06-03 11:59 ` Hans de Goede
2021-06-03 13:48 ` Emil Velikov
2021-04-21 20:47 ` [PATCH v2 3/9] drm/privacy-screen: Add X86 specific arch init code Hans de Goede
2021-04-21 20:47 ` [PATCH v2 4/9] drm/privacy-screen: Add notifier support Hans de Goede
2021-04-21 20:48 ` [PATCH v2 5/9] drm/connector: Add a drm_connector privacy-screen helper functions Hans de Goede
2021-04-21 20:48 ` [PATCH v2 6/9] platform/x86: thinkpad_acpi: Add hotkey_notify_extended_hotkey() helper Hans de Goede
2021-04-21 20:48 ` [PATCH v2 7/9] platform/x86: thinkpad_acpi: Get privacy-screen / lcdshadow ACPI handles only once Hans de Goede
2021-04-21 20:48 ` [PATCH v2 8/9] platform/x86: thinkpad_acpi: Register a privacy-screen device Hans de Goede
2021-04-21 20:48 ` [PATCH v2 9/9] drm/i915: Add privacy-screen support Hans de Goede
2021-04-22 8:51 ` [PATCH v2 0/9] drm: Add privacy-screen class and connector properties Simon Ser
2021-04-22 8:54 ` Hans de Goede
2021-04-22 8:58 ` Simon Ser [this message]
2021-04-27 17:03 ` Marco Trevisan
2021-07-13 19:25 ` Rajat Jain
2021-08-03 15:20 ` Marco Trevisan
2021-08-03 20:50 ` Rajat Jain
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='xVZdxPoOewlP5LmxWy2EHKEIxRw1oeQH9xfPG5a6i8O5IJf5AqpFelwBSIoacwhIqCWJG0sqzHpfGL3WqAxM0CZOUyCOPUuCToD8Ia1Dwjw=@emersion.fr' \
--to=contact@emersion.fr \
--cc=airlied@linux.ie \
--cc=andy@infradead.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=marco.trevisan@canonical.com \
--cc=mario.limonciello@outlook.com \
--cc=markpearson@lenovo.com \
--cc=mgross@linux.intel.com \
--cc=pekka.paalanen@collabora.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rajatja@google.com \
--cc=rodrigo.vivi@intel.com \
--cc=seb128@ubuntu.com \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).