diff options
author | Rodrigo Vivi <rodrigo.vivi@intel.com> | 2021-10-06 12:03:44 -0400 |
---|---|---|
committer | Rodrigo Vivi <rodrigo.vivi@intel.com> | 2021-10-07 13:04:58 -0400 |
commit | 910b5caac6625d2bf0b6c1dde502451431bd0159 (patch) | |
tree | e93f124f858d97dc8310b89a34ca4fb92bf6e63d /README.md | |
parent | 25d2f85bf57fb0a56eeb60d00465b99f069f4376 (diff) |
README.md: Accept the i915_drm.h standalone update.
Looking to our git log we can see that the most common case
is the update of the single i915_drm.h file.
There are some advantages of doing this standalone update:
1. Make reviews easier without the noise of other headers.
2. Avoid the developer to have to touch other areas that are
not immediately related to targeted work.
Cc: Petri Latvala <petri.latvala@intel.com>
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Reviewed-by: Petri Latvala <petri.latvala@intel.com>
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 14 |
1 files changed, 14 insertions, 0 deletions
@@ -159,6 +159,20 @@ These should be updated all together by: Then, commit with a note of which exact commit from airlied's branch was used to generate them. +### `include/drm-uapi/i915_drm.h` + +Imported i915_drm.h uapi headers from airlied's drm-next branch. + +In some cases updating a single uapi file is needed as our history +shows. So in this case, it should be done by: + + # From the kernel dir with a drm/drm-next commit checked out: + $ make INSTALL_HDR_PATH=<dest-dir> headers_install + $ cp <dest-dir>/include/drm/i915_drm.h <igt-dir>/include/drm-uapi/ + +Then, commit with a note of which exact commit from airlied's branch +was used to generate it. + ### `include/linux-uapi/sync_file.h` Imported non-DRM uapi headers from airlied's drm-next branch. |