From: Matthew Auld <matthew.auld@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 0/2] doc/rfc for small BAR support
Date: Fri, 18 Feb 2022 11:22:40 +0000 [thread overview]
Message-ID: <20220218112242.2117968-1-matthew.auld@intel.com> (raw)
The new bits of proposed uAPI for the upcoming small BAR support.
--
2.34.1
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Auld <matthew.auld@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: [PATCH 0/2] doc/rfc for small BAR support
Date: Fri, 18 Feb 2022 11:22:40 +0000 [thread overview]
Message-ID: <20220218112242.2117968-1-matthew.auld@intel.com> (raw)
The new bits of proposed uAPI for the upcoming small BAR support.
--
2.34.1
next reply other threads:[~2022-02-18 11:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 11:22 Matthew Auld [this message]
2022-02-18 11:22 ` [PATCH 0/2] doc/rfc for small BAR support Matthew Auld
2022-02-18 11:22 ` [Intel-gfx] [PATCH 1/2] drm/doc: remove rfc section for dg1 Matthew Auld
2022-02-18 11:22 ` Matthew Auld
2022-02-18 18:30 ` [Intel-gfx] " Lucas De Marchi
2022-02-18 11:22 ` [Intel-gfx] [PATCH 2/2] drm/doc: add rfc section for small BAR uapi Matthew Auld
2022-02-18 11:22 ` Matthew Auld
2022-02-22 10:36 ` [Intel-gfx] " Thomas Hellström
2022-02-22 10:36 ` Thomas Hellström
2022-02-22 17:39 ` [Intel-gfx] " Abodunrin, Akeem G
2022-02-22 17:39 ` Abodunrin, Akeem G
2022-03-18 9:38 ` [Intel-gfx] " Lionel Landwerlin
2022-03-18 10:21 ` Matthew Auld
2022-02-18 14:15 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for doc/rfc for small BAR support Patchwork
2022-02-18 14:45 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
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=20220218112242.2117968-1-matthew.auld@intel.com \
--to=matthew.auld@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
/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.