From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Petri Latvala <petri.latvala@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] lib: sync i915_pciids.h with kernel
Date: Fri, 23 Oct 2020 08:55:58 -0700 [thread overview]
Message-ID: <87lffxgcmp.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20201023080324.GR7444@platvala-desk.ger.corp.intel.com>
On Fri, 23 Oct 2020 01:03:24 -0700, Petri Latvala wrote:
>
> On Fri, Oct 23, 2020 at 10:59:27AM +0300, Petri Latvala wrote:
> > On Thu, Oct 22, 2020 at 08:18:59PM -0700, Ashutosh Dixit wrote:
> > > Align with kernel commits:
> > >
> > > 605f9c290c1a2 ("drm/i915: Sort ICL PCI IDs")
> > > 514dc424ce4f5 ("drm/i915: Sort CNL PCI IDs")
> > > 32d4ec9a1681d ("drm/i915: Sort CFL PCI IDs")
> > > df3478af1d73c ("drm/i915: Sort CML PCI IDs")
> > > cd988984cbea0 ("drm/i915: Sort KBL PCI IDs")
> > > b04d36f737712 ("drm/i915: Sort SKL PCI IDs")
> > > 9c0b2d30441b5 ("drm/i915: Sort HSW PCI IDs")
> > > 79033a0a78984 ("drm/i915: Ocd the HSW PCI ID hex numbers")
> > > cfb3db8fdae25 ("drm/i915: Try to fix the SKL GT3/4 vs. GT3e/4e comments")
> > > 03e399020cd20 ("drm/i915: Add SKL GT1.5 PCI IDs")
> > > 812f044df08cc ("drm/i915: Reclassify SKL 0x1923 and 0x1927 as ULT")
> > > 194909a32aed0 ("drm/i915: Reclassify SKL 0x192a as GT3")
> > > 82e84284ab7dd ("drm/i915: Update Haswell PCI IDs")
> > > 24ea098b7c0d8 ("drm/i915/jsl: Split EHL/JSL platform info and PCI ids")
> > > b50b7991b739c ("drm/i915/dg1: add more PCI ids")
> > >
> > > Cc: Petri Latvala <petri.latvala@intel.com>
> > > Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> > > ---
> >
> > I get really confused by commit messages like this. Which commit is
> > this now copied from, and which repo has that commit?
Hi Petri, yes I wasn't happy either doing this since it appears a simple
commit message like "Sync i915_pciids.h with the drm-tip kernel as of
today" should have been sufficient. But the previous git log for the file
has followed this format for the commit message. The format is the same as
that for "git log --oneline" for include/drm/i915_pciids.h on drm-tip,
newest commits on top.
But yes, I should have said it's the drm-tip kernel.
> Regardless of that confusion, the file matches what's in drm-tip so
>
> Reviewed-by: Petri Latvala <petri.latvala@intel.com>
Thanks.
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-10-23 15:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 3:18 [igt-dev] [PATCH i-g-t] lib: sync i915_pciids.h with kernel Ashutosh Dixit
2020-10-23 4:06 ` [igt-dev] ✓ Fi.CI.BAT: success for lib: sync i915_pciids.h with kernel (rev8) Patchwork
2020-10-23 5:06 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2020-10-23 7:59 ` [igt-dev] [PATCH i-g-t] lib: sync i915_pciids.h with kernel Petri Latvala
2020-10-23 8:03 ` Petri Latvala
2020-10-23 15:55 ` Dixit, Ashutosh [this message]
2020-10-26 8:30 ` Petri Latvala
-- strict thread matches above, loose matches on Subject: below --
2022-07-27 4:34 Matt Roper
2021-06-03 14:31 Matt Roper
2021-06-03 15:05 ` James Ausmus
2021-06-03 18:58 ` Srivatsa, Anusha
2020-10-23 1:05 Ashutosh Dixit
2020-03-20 0:13 [igt-dev] [PATCH i-g-t] lib: Sync " Swathi Dhanavanthri
2020-03-25 20:48 ` Matt Roper
2019-02-02 8:08 [igt-dev] [PATCH i-g-t] lib: sync " Rodrigo Vivi
2019-02-04 18:12 ` Lionel Landwerlin
2019-02-04 18:46 ` Souza, Jose
2019-02-04 18:47 ` Rodrigo Vivi
2018-10-12 21:39 [igt-dev] ✗ Fi.CI.BAT: failure for " Souza, Jose
2018-10-12 22:40 ` [igt-dev] [PATCH i-g-t] " Rodrigo Vivi
2018-10-12 23:16 ` Souza, Jose
2018-10-15 16:02 ` Rodrigo Vivi
2018-10-12 20:27 Rodrigo Vivi
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=87lffxgcmp.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@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 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.