From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Petri Latvala <petri.latvala@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 8/8] README.md: Accept the i915_drm.h standalone update.
Date: Thu, 7 Oct 2021 13:09:19 -0400 [thread overview]
Message-ID: <YV8pv4qi9jAJw18P@intel.com> (raw)
In-Reply-To: <YV6vamfWa+8n4oh7@platvala-desk.ger.corp.intel.com>
On Thu, Oct 07, 2021 at 11:27:22AM +0300, Petri Latvala wrote:
> On Wed, Oct 06, 2021 at 12:14:44PM -0400, Rodrigo Vivi wrote:
> > 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>
Thank you. Pushed the remaining patches just now.
>
>
> > ---
> > README.md | 14 ++++++++++++++
> > 1 file changed, 14 insertions(+)
> >
> > diff --git a/README.md b/README.md
> > index 62bef46d..66f2bc0f 100644
> > --- a/README.md
> > +++ b/README.md
> > @@ -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.
> > --
> > 2.31.1
> >
next prev parent reply other threads:[~2021-10-07 17:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 16:14 [igt-dev] [PATCH i-g-t 0/8] drm-uapi clean-up Rodrigo Vivi
2021-10-06 16:14 ` [igt-dev] [PATCH i-g-t 1/8] tests/i915/gem_pxp: Add LOCAL_ UAPI defines Rodrigo Vivi
2021-10-06 17:17 ` Dixit, Ashutosh
2021-10-06 17:25 ` Rodrigo Vivi
2021-10-06 17:32 ` Dixit, Ashutosh
2021-10-06 17:40 ` Teres Alexis, Alan Previn
2021-10-07 8:19 ` Petri Latvala
2021-10-06 17:37 ` Rodrigo Vivi
2021-10-06 18:09 ` Dixit, Ashutosh
2021-10-06 19:40 ` Vivi, Rodrigo
2021-10-06 20:19 ` Dixit, Ashutosh
2021-10-06 16:14 ` [igt-dev] [PATCH i-g-t 2/8] Revert "i915_drm.h sync" Rodrigo Vivi
2021-10-06 16:14 ` [igt-dev] [PATCH i-g-t 3/8] i915_drm.h sync with drm-next Rodrigo Vivi
2021-10-07 12:34 ` Petri Latvala
2021-10-06 16:14 ` [igt-dev] [PATCH i-g-t 4/8] tests/gem_userptr_blits: Remove LOCAL_ Rodrigo Vivi
2021-10-07 12:36 ` Petri Latvala
2021-10-06 16:14 ` [igt-dev] [PATCH i-g-t 5/8] include/drm-uapi: Sync with drm-next Rodrigo Vivi
2021-10-07 12:35 ` Petri Latvala
2021-10-06 16:14 ` [igt-dev] [PATCH i-g-t 6/8] README.md: Detail the drm-uapi headers sync Rodrigo Vivi
2021-10-07 8:27 ` Petri Latvala
2021-10-06 16:14 ` [igt-dev] [PATCH i-g-t 7/8] include: Introduce linux-uapi for non-drm-uapi files Rodrigo Vivi
2021-10-06 17:39 ` Dixit, Ashutosh
2021-10-06 17:56 ` Vivi, Rodrigo
2021-10-06 18:25 ` Dixit, Ashutosh
2021-10-07 8:23 ` Petri Latvala
2021-10-07 12:33 ` Petri Latvala
2021-10-06 16:14 ` [igt-dev] [PATCH i-g-t 8/8] README.md: Accept the i915_drm.h standalone update Rodrigo Vivi
2021-10-07 8:27 ` Petri Latvala
2021-10-07 17:09 ` Rodrigo Vivi [this message]
2021-10-06 17:16 ` [igt-dev] ✓ Fi.CI.BAT: success for drm-uapi clean-up Patchwork
2021-10-06 20:10 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=YV8pv4qi9jAJw18P@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=petri.latvala@intel.com \
/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