From: Simon Ser <contact@emersion.fr>
To: "Michał Winiarski" <michal.winiarski@intel.com>
Cc: David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH v2 1/2] drm: Expand max DRM device number to full MINORBITS
Date: Wed, 24 Aug 2022 08:02:35 +0000 [thread overview]
Message-ID: <iZUuSfDNvqc_qcWivCeUNyKzQ91mykNMLfbE205fylYTMxTkh4mCNzftDhsBDZX3QJwEd9bG9RGHD5QnHlyfiOz4BJDCZUriwoT45S6eAJ8=@emersion.fr> (raw)
In-Reply-To: <20220823210612.296922-2-michal.winiarski@intel.com>
This approach will not break existing user-space AFAIK.
Acked-by: Simon Ser <contact@emersion.fr>
next prev parent reply other threads:[~2022-08-24 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 21:06 [PATCH v2 0/2] drm: Use full allocated minor range for DRM Michał Winiarski
2022-08-23 21:06 ` [PATCH v2 1/2] drm: Expand max DRM device number to full MINORBITS Michał Winiarski
2022-08-24 8:02 ` Simon Ser [this message]
2022-08-23 21:06 ` [PATCH v2 2/2] drm: Use mutex for minors Michał Winiarski
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='iZUuSfDNvqc_qcWivCeUNyKzQ91mykNMLfbE205fylYTMxTkh4mCNzftDhsBDZX3QJwEd9bG9RGHD5QnHlyfiOz4BJDCZUriwoT45S6eAJ8=@emersion.fr' \
--to=contact@emersion.fr \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=michal.winiarski@intel.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).