From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>,
Matthew Auld <matthew.william.auld@gmail.com>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Intel Graphics Development" <intel-gfx@lists.freedesktop.org>,
"Matthew Auld" <matthew.auld@intel.com>,
"ML dri-devel" <dri-devel@lists.freedesktop.org>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH] drm/i915: allow DG1 autoprobe for CONFIG_BROKEN
Date: Wed, 23 Jun 2021 16:03:39 +0300 [thread overview]
Message-ID: <87zgvgu40k.fsf@intel.com> (raw)
In-Reply-To: <YMuEYsMqbOUW7A2T@phenom.ffwll.local>
On Thu, 17 Jun 2021, Daniel Vetter <daniel@ffwll.ch> wrote:
> I think stuffing this into topic/core-for-CI is fine, lets wait a bit more
> until mesa and everything is ready with adding the pciids to an official
> tree.
On a related note, I think we'll need rationale documented for each
commit in topic/core-for-CI going forward. Why is the commit in
topic/core-for-CI? What's the plan for moving it out? Etc.
topic/core-for-CI has become a dumping ground for odd patches without
proper rationale why they exist. The ideal is zero commits in the
branch.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>,
Matthew Auld <matthew.william.auld@gmail.com>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Intel Graphics Development" <intel-gfx@lists.freedesktop.org>,
"Matthew Auld" <matthew.auld@intel.com>,
"ML dri-devel" <dri-devel@lists.freedesktop.org>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: allow DG1 autoprobe for CONFIG_BROKEN
Date: Wed, 23 Jun 2021 16:03:39 +0300 [thread overview]
Message-ID: <87zgvgu40k.fsf@intel.com> (raw)
In-Reply-To: <YMuEYsMqbOUW7A2T@phenom.ffwll.local>
On Thu, 17 Jun 2021, Daniel Vetter <daniel@ffwll.ch> wrote:
> I think stuffing this into topic/core-for-CI is fine, lets wait a bit more
> until mesa and everything is ready with adding the pciids to an official
> tree.
On a related note, I think we'll need rationale documented for each
commit in topic/core-for-CI going forward. Why is the commit in
topic/core-for-CI? What's the plan for moving it out? Etc.
topic/core-for-CI has become a dumping ground for odd patches without
proper rationale why they exist. The ideal is zero commits in the
branch.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-06-23 13:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 9:22 [PATCH] drm/i915: allow DG1 autoprobe for CONFIG_BROKEN Matthew Auld
2021-06-14 9:22 ` [Intel-gfx] " Matthew Auld
2021-06-14 9:31 ` Thomas Hellström
2021-06-14 9:31 ` [Intel-gfx] " Thomas Hellström
2021-06-14 9:41 ` Maarten Lankhorst
2021-06-14 9:41 ` Maarten Lankhorst
2021-06-14 16:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-06-14 20:14 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-06-16 14:29 ` [PATCH] " Matthew Auld
2021-06-16 14:29 ` [Intel-gfx] " Matthew Auld
2021-06-17 17:20 ` Daniel Vetter
2021-06-17 17:20 ` [Intel-gfx] " Daniel Vetter
2021-06-23 13:03 ` Jani Nikula [this message]
2021-06-23 13:03 ` Jani Nikula
2021-06-18 19:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: allow DG1 autoprobe for CONFIG_BROKEN (rev2) Patchwork
2021-06-18 22:51 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=87zgvgu40k.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=matthew.william.auld@gmail.com \
--cc=thomas.hellstrom@linux.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.