dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: "DRM maintainer tools announcements, discussion,
	and development" <dim-tools@lists.freedesktop.org>,
	Maxime Ripard <maxime.ripard@bootlin.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PULL] drm-intel-next-fixes
Date: Fri, 19 Oct 2018 12:41:48 +0300	[thread overview]
Message-ID: <153994210865.27705.2758402152067401702@jlahtine-desk.ger.corp.intel.com> (raw)
In-Reply-To: <CAKMK7uE3z2GdC5eN3+0FLkTL3f4NjsZ=Gunhtc98JBHT1vcouA@mail.gmail.com>

Quoting Daniel Vetter (2018-10-19 10:05:32)
> On Fri, Oct 19, 2018 at 8:59 AM Joonas Lahtinen
> <joonas.lahtinen@linux.intel.com> wrote:
> >
> > Quoting Daniel Vetter (2018-10-18 22:32:00)
> > > On Thu, Oct 18, 2018 at 6:57 PM Joonas Lahtinen
> > > <joonas.lahtinen@linux.intel.com> wrote:
> > > >
> > > > Hi Dave,
> > > >
> > > > Here comes the final set of fixes under -next-fixes umbrella.
> > > > Next one will be then from -fixes, assuming a release next Sun.
> > > >
> > > > Fixes for bunch of display related issues reported by users, then the
> > > > MST fixes that were dropped from Rodrigos PR + further Icelake fixes
> > > > and proactive improvements picked by tooling.
> > > >
> > > > Excuse for the slight accumulation as I skipped last week due to
> > > > travel like I warned.
> > > >
> > > > Regards, Joonas
> > > >
> > > > ***
> > > >
> > > > drm-intel-next-fixes-2018-10-18:
> > > > - Fix GPU hang on MacBook2,1 when booting in EFI mode (Bugzilla #105637)
> > > > - Fix garbled console on Y tiled BIOS framebuffer configs (Bugzilla #108264)
> > > > - Fix black screen on certain eDP panels eg. Dell XPS 9350 (Bugzilla #107489 and #105338)
> > > > - MST fixes that Rodrigo dropped from drm-intel-fixes and bunch of Icelake fixes
> > >
> > > This won't work because it doesn't contain Lyude's core fix (+ the 2
> > > fixups). You either need to cherry-pick all of them (and then probably
> > > include the nouveau one), or none of them. Did the cherry-pick script
> > > not propose them, or something else? They're all cc: stable.
> >
> > cherry-pick-next-fixes did not propose more. I did specifically ask
> > Rodrigo to drop the relevant stuff from drm-intel-fixes so that the
> > tooling would pick it up. What is there that is missing?
> 
> dim cherry-pick-branch is limited to drivers/gpu/drm/i915 :-(
> 
> Remove that (well at least only filter drm/) and you should see them.
> Ideally you put the core patch + 2 core fixups before the i915/nouveau
> patches.
> 
> I guess putting core patches that are bugfixes through drm-intel.git
> really isn't a good idea with our process ...

I've now done this now. Removal of the filter adding two patches, but I
had to track down the further Fixes: to Fixes: manually. Thanks to
Daniel for the assistance in pointing the missing patches.

As you already pulled this PR, the core fixes will end up after
the i915 fixes. If you end up wanting to rebase the order, note that
the Fixes: annotations will be wrecked. I'll send a further fixup PR.

I also amended the Fixes: tags to point to cherry-picked fixes, to
decrease the likelihood of falling through automated tooling (while
appending Cc: stable to one patch missing it).

So you want to avoid rebasing the patches in all circumstances (or
you have to update/remove the Fixes: lines beyond the line "(cherry
picked from ...".

Lovely thing to do on Friday :) Hopefully next week will be less
of a hassle.

Regards, Joonas

> -Daniel
> 
> >
> > Regards, Joonas
> >
> > > -Daniel
> > >
> > > > - Then assorted proactive code fixes caught by CI or developers
> > > >
> > > > The following changes since commit ca4b869240d5810ebac6b1570ad7beffcfbac2f5:
> > > >
> > > >   Merge branch 'drm-next-4.20' of git://people.freedesktop.org/~agd5f/linux into drm-next (2018-10-11 14:53:45 +1000)
> > > >
> > > > are available in the Git repository at:
> > > >
> > > >   git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-fixes-2018-10-18
> > > >
> > > > for you to fetch changes up to 835fe6d75d14c1513910ed7f5665127fee12acc8:
> > > >
> > > >   firmware/dmc/icl: Add missing MODULE_FIRMWARE() for Icelake. (2018-10-18 10:36:10 +0300)
> > > >
> > > > ----------------------------------------------------------------
> > > > - Fix GPU hang on MacBook2,1 when booting in EFI mode (Bugzilla #105637)
> > > > - Fix garbled console on Y tiled BIOS framebuffer configs (Bugzilla #108264)
> > > > - Fix black screen on certain eDP panels eg. Dell XPS 9350 (Bugzilla #107489 and #105338)
> > > > - MST fixes that Rodrigo dropped from drm-intel-fixes and bunch of Icelake fixes
> > > > - Then assorted proactive code fixes caught by CI or developers
> > > >
> > > > ----------------------------------------------------------------
> > > > Anusha Srivatsa (1):
> > > >       firmware/dmc/icl: Add missing MODULE_FIRMWARE() for Icelake.
> > > >
> > > > Chris Wilson (3):
> > > >       drm/i915: Only reset seqno if actually idle
> > > >       drm/i915/selftests: Disable shrinker across mmap-exhaustion
> > > >       drm/i915: Large page offsets for pread/pwrite
> > > >
> > > > Imre Deak (1):
> > > >       drm/i915/gen9+: Fix initial readout for Y tiled framebuffers
> > > >
> > > > Lyude Paul (3):
> > > >       drm/i915: Don't unset intel_connector->mst_port
> > > >       drm/i915: Skip vcpi allocation for MSTB ports that are gone
> > > >       drm/i915: Fix intel_dp_mst_best_encoder()
> > > >
> > > > Mahesh Kumar (2):
> > > >       drm/i915/icl: create function to identify combophy port
> > > >       drm/i915/icl: Fix DDI/TC port clk_off bits
> > > >
> > > > Manasi Navare (1):
> > > >       drm/i915/dp: Link train Fallback on eDP only if fallback link BW can fit panel's native mode
> > > >
> > > > Rodrigo Vivi (1):
> > > >       drm/i915/icl: Fix signal_levels
> > > >
> > > > Ville Syrjälä (3):
> > > >       drm/i915: Check fb stride against plane max stride
> > > >       drm/i915: Restore vblank interrupts earlier
> > > >       drm/i915: Use the correct crtc when sanitizing plane mapping
> > > >
> > > >  drivers/gpu/drm/i915/i915_debugfs.c              |   2 +-
> > > >  drivers/gpu/drm/i915/i915_gem.c                  |  12 +-
> > > >  drivers/gpu/drm/i915/i915_reg.h                  |   3 +
> > > >  drivers/gpu/drm/i915/intel_csr.c                 |   1 +
> > > >  drivers/gpu/drm/i915/intel_ddi.c                 |  36 ++++--
> > > >  drivers/gpu/drm/i915/intel_display.c             | 151 ++++++++++++++++-------
> > > >  drivers/gpu/drm/i915/intel_dp.c                  |  32 ++++-
> > > >  drivers/gpu/drm/i915/intel_dp_link_training.c    |  26 ++--
> > > >  drivers/gpu/drm/i915/intel_dp_mst.c              |  41 +++---
> > > >  drivers/gpu/drm/i915/intel_drv.h                 |   2 +
> > > >  drivers/gpu/drm/i915/intel_sprite.c              |  22 ++++
> > > >  drivers/gpu/drm/i915/selftests/i915_gem_object.c |   3 +
> > > >  12 files changed, 227 insertions(+), 104 deletions(-)
> > >
> > >
> > >
> > > --
> > > Daniel Vetter
> > > Software Engineer, Intel Corporation
> > > +41 (0) 79 365 57 48 - http://blog.ffwll.ch
> 
> 
> 
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-10-19  9:41 UTC|newest]

Thread overview: 126+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18 16:57 [PULL] drm-intel-next-fixes Joonas Lahtinen
2018-10-18 19:32 ` Daniel Vetter
2018-10-19  6:59   ` Joonas Lahtinen
2018-10-19  7:05     ` Daniel Vetter
2018-10-19  9:41       ` Joonas Lahtinen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-19  8:30 Joonas Lahtinen
2024-01-11 10:51 Joonas Lahtinen
2023-11-08 14:04 Jani Nikula
2023-11-10 15:48 ` Daniel Vetter
2023-08-31 21:28 Rodrigo Vivi
2023-08-24 12:34 Rodrigo Vivi
2023-07-06  8:24 Tvrtko Ursulin
2023-06-29 10:02 Tvrtko Ursulin
2023-06-21  9:54 Tvrtko Ursulin
2023-05-04 13:01 Joonas Lahtinen
2023-04-27 11:23 Joonas Lahtinen
2023-04-20  8:12 Joonas Lahtinen
2023-04-13 12:12 Joonas Lahtinen
2023-04-13 18:47 ` Daniel Vetter
2023-02-27 10:17 Jani Nikula
2023-02-17 12:24 Jani Nikula
2022-12-15 20:36 Rodrigo Vivi
2022-12-01 16:40 Rodrigo Vivi
2022-10-13 12:56 Tvrtko Ursulin
2022-10-06 10:18 Tvrtko Ursulin
2022-09-29 14:26 Tvrtko Ursulin
2022-08-11 21:03 Rodrigo Vivi
2022-08-04 17:33 Rodrigo Vivi
2022-05-24 13:59 Jani Nikula
2022-03-24  8:44 Tvrtko Ursulin
2022-03-17  7:47 Joonas Lahtinen
2022-03-10  7:58 Joonas Lahtinen
2022-01-20 10:13 Tvrtko Ursulin
2022-01-13  9:33 Tvrtko Ursulin
2022-01-14 13:23 ` Daniel Vetter
2021-11-09 23:17 Rodrigo Vivi
2021-08-26  9:03 Jani Nikula
2021-07-07 15:09 Rodrigo Vivi
2021-06-29 18:54 Rodrigo Vivi
2021-06-30 10:05 ` Jani Nikula
2021-06-30 19:04   ` Rodrigo Vivi
2021-07-01  8:57     ` Jani Nikula
2021-02-25 14:43 Rodrigo Vivi
2021-02-18 22:46 Rodrigo Vivi
2020-12-18 15:04 Jani Nikula
2020-12-18 15:42 ` Daniel Vetter
2020-10-22 20:56 Rodrigo Vivi
2020-10-15 18:14 Rodrigo Vivi
2020-10-02 18:26 Rodrigo Vivi
2020-07-30 16:26 Joonas Lahtinen
2020-08-10  7:31 ` Dave Airlie
2020-08-12 12:49   ` Jani Nikula
2020-06-10  9:37 Joonas Lahtinen
2020-06-10 11:19 ` Joonas Lahtinen
2020-06-04 15:04 Joonas Lahtinen
2020-05-28 14:40 Joonas Lahtinen
2020-05-20 12:32 Joonas Lahtinen
2020-04-08 21:59 Rodrigo Vivi
2020-04-02 21:30 Rodrigo Vivi
2020-03-27  8:16 Rodrigo Vivi
2019-12-05  9:24 Joonas Lahtinen
2019-11-28 14:15 Joonas Lahtinen
2019-11-22 15:55 Joonas Lahtinen
2019-11-20 20:40 Joonas Lahtinen
2019-11-22 12:08 ` Joonas Lahtinen
2019-11-14  8:52 Joonas Lahtinen
2019-11-07 14:50 Joonas Lahtinen
2019-09-27 19:49 Rodrigo Vivi
2019-09-19 14:16 Rodrigo Vivi
2019-09-11 23:33 Rodrigo Vivi
2019-05-15  7:48 Joonas Lahtinen
2019-05-09 10:01 Joonas Lahtinen
2019-05-02 13:40 Joonas Lahtinen
2019-04-30  7:08 Joonas Lahtinen
2019-04-25  6:13 Joonas Lahtinen
2019-03-12 20:55 Rodrigo Vivi
2018-12-27  7:40 Jani Nikula
2018-10-25 13:18 Joonas Lahtinen
2018-10-19 10:37 Joonas Lahtinen
2018-10-19 12:34 ` Daniel Vetter
2018-10-04 13:37 Joonas Lahtinen
2018-08-24 21:48 Rodrigo Vivi
2018-08-16 19:03 Rodrigo Vivi
2018-08-06 23:30 Rodrigo Vivi
2018-04-19  9:30 Joonas Lahtinen
2018-03-27 14:58 Joonas Lahtinen
2018-03-22 14:35 Joonas Lahtinen
2018-02-07 20:44 Rodrigo Vivi
2018-02-02  0:45 Rodrigo Vivi
2017-11-23  9:34 Jani Nikula
2017-11-10 13:21 Jani Nikula
2017-07-11 13:07 Jani Nikula
2017-06-27  8:28 Daniel Vetter
2017-02-17  9:46 Jani Nikula
2017-02-15 14:06 Jani Nikula
2016-12-22 10:22 Jani Nikula
2016-12-07 19:45 Jani Nikula
2016-10-11 14:09 Jani Nikula
2016-08-05 13:27 Jani Nikula
2016-07-25  6:41 Daniel Vetter
2016-05-25  8:57 Jani Nikula
2016-03-16 11:04 Jani Nikula
2016-01-14 20:06 Jani Nikula
2015-11-06 13:43 Jani Nikula
2015-10-22  8:28 Daniel Vetter
2015-09-02 11:49 Jani Nikula
2015-08-28 12:44 Jani Nikula
2015-08-16 18:13 Daniel Vetter
2015-07-02 11:26 Jani Nikula
2015-06-22 10:33 Jani Nikula
2015-06-18  6:04 Jani Nikula
2015-06-19  3:48 ` Dave Airlie
2015-06-19 15:24   ` Daniel Vetter
2015-06-22  7:59     ` Ander Conselvan De Oliveira
2015-06-22  8:12       ` Jani Nikula
2015-06-22  8:13         ` Dave Airlie
2015-06-11  8:40 Jani Nikula
2015-05-29 17:39 Daniel Vetter
2015-04-24 21:46 Jani Nikula
2015-04-15 12:21 Jani Nikula
2015-02-11 11:09 Jani Nikula
2015-02-11 11:48 ` Daniel Vetter
2014-12-30 12:47 Jani Nikula
2014-12-17 12:16 Jani Nikula
2014-12-11 13:43 Jani Nikula
2014-12-04  9:56 Daniel Vetter

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=153994210865.27705.2758402152067401702@jlahtine-desk.ger.corp.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dim-tools@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=maxime.ripard@bootlin.com \
    --cc=rodrigo.vivi@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;
as well as URLs for NNTP newsgroup(s).