All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: dim-tools@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org,
	Maxime Ripard <mripard@kernel.org>,
	dri-devel@lists.freedesktop.org, Dave Airlie <airlied@gmail.com>
Subject: Re: [Intel-gfx] [PULL] drm-intel-next-fixes
Date: Wed, 30 Jun 2021 15:04:54 -0400	[thread overview]
Message-ID: <YNzAViVC1l4hE/uG@intel.com> (raw)
In-Reply-To: <87zgv7r7kg.fsf@intel.com>

On Wed, Jun 30, 2021 at 01:05:35PM +0300, Jani Nikula wrote:
> On Tue, 29 Jun 2021, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> > Hi Dave and Daniel,
> >
> > Here goes drm-intel-next-fixes-2021-06-29:
> >
> > The biggest fix is the restoration of mmap ioctl for gen12 integrated parts
> > which lack was breaking ADL-P with media stack.
> > Besides that a small selftest fix and a theoretical overflow on
> > i915->pipe_to_crtc_mapping.
> 
> My last fixes pull for v5.13 fell between the cracks [1]. There was one
> stable worthy fix, but since it was still in drm-intel-fixes when you
> ran dim cherry-pick-next-fixes, it was skipped for drm-intel-next-fixes.
> 
> I've now dropped the commit and pushed v5.13 to drm-intel-fixes, as
> we're past that point. Subsequent dim cherry-pick-next-fixes should pick
> it up now.

it didn't, probably because the Fixes hash not being part of the drm-next yet?!

I can cherry-pick that directly. Please let me know the commit id.

Thanks,
Rodrigo.

> 
> Please do another next fixes pull request with that. (It's okay to pull
> this one already though, doesn't make a difference.)
> 
> 
> BR,
> Jani.
> 
> 
> [1] https://lore.kernel.org/r/87czsbu15r.fsf@intel.com
> 
> 
> 
> >
> > Thanks,
> > Rodrigo.
> >
> > The following changes since commit 1bd8a7dc28c1c410f1ceefae1f2a97c06d1a67c2:
> >
> >   Merge tag 'exynos-drm-next-for-v5.14' of git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into drm-next (2021-06-11 14:19:12 +1000)
> >
> > are available in the Git repository at:
> >
> >   git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-fixes-2021-06-29
> >
> > for you to fetch changes up to c90c4c6574f3feaf2203b5671db1907a1e15c653:
> >
> >   drm/i915: Reinstate the mmap ioctl for some platforms (2021-06-28 07:43:56 -0400)
> >
> > ----------------------------------------------------------------
> > The biggest fix is the restoration of mmap ioctl for gen12 integrated parts
> > which lack was breaking ADL-P with media stack.
> > Besides that a small selftest fix and a theoretical overflow on
> > i915->pipe_to_crtc_mapping.
> >
> > ----------------------------------------------------------------
> > Chris Wilson (1):
> >       drm/i915/selftests: Reorder tasklet_disable vs local_bh_disable
> >
> > Jani Nikula (1):
> >       drm/i915/dsc: abstract helpers to get bigjoiner primary/secondary crtc
> >
> > Thomas Hellström (1):
> >       drm/i915: Reinstate the mmap ioctl for some platforms
> >
> >  drivers/gpu/drm/i915/display/intel_display.c       |  7 ++-
> >  drivers/gpu/drm/i915/display/intel_display_types.h |  8 ++++
> >  drivers/gpu/drm/i915/display/intel_vdsc.c          | 40 +++++++++++-----
> >  drivers/gpu/drm/i915/display/intel_vdsc.h          |  1 +
> >  drivers/gpu/drm/i915/gem/i915_gem_mman.c           |  7 +--
> >  drivers/gpu/drm/i915/gt/selftest_execlists.c       | 55 +++++++++++++---------
> >  6 files changed, 76 insertions(+), 42 deletions(-)
> 
> -- 
> Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: dim-tools@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	Sean Paul <sean@poorly.run>
Subject: Re: [PULL] drm-intel-next-fixes
Date: Wed, 30 Jun 2021 15:04:54 -0400	[thread overview]
Message-ID: <YNzAViVC1l4hE/uG@intel.com> (raw)
In-Reply-To: <87zgv7r7kg.fsf@intel.com>

On Wed, Jun 30, 2021 at 01:05:35PM +0300, Jani Nikula wrote:
> On Tue, 29 Jun 2021, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> > Hi Dave and Daniel,
> >
> > Here goes drm-intel-next-fixes-2021-06-29:
> >
> > The biggest fix is the restoration of mmap ioctl for gen12 integrated parts
> > which lack was breaking ADL-P with media stack.
> > Besides that a small selftest fix and a theoretical overflow on
> > i915->pipe_to_crtc_mapping.
> 
> My last fixes pull for v5.13 fell between the cracks [1]. There was one
> stable worthy fix, but since it was still in drm-intel-fixes when you
> ran dim cherry-pick-next-fixes, it was skipped for drm-intel-next-fixes.
> 
> I've now dropped the commit and pushed v5.13 to drm-intel-fixes, as
> we're past that point. Subsequent dim cherry-pick-next-fixes should pick
> it up now.

it didn't, probably because the Fixes hash not being part of the drm-next yet?!

I can cherry-pick that directly. Please let me know the commit id.

Thanks,
Rodrigo.

> 
> Please do another next fixes pull request with that. (It's okay to pull
> this one already though, doesn't make a difference.)
> 
> 
> BR,
> Jani.
> 
> 
> [1] https://lore.kernel.org/r/87czsbu15r.fsf@intel.com
> 
> 
> 
> >
> > Thanks,
> > Rodrigo.
> >
> > The following changes since commit 1bd8a7dc28c1c410f1ceefae1f2a97c06d1a67c2:
> >
> >   Merge tag 'exynos-drm-next-for-v5.14' of git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into drm-next (2021-06-11 14:19:12 +1000)
> >
> > are available in the Git repository at:
> >
> >   git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-fixes-2021-06-29
> >
> > for you to fetch changes up to c90c4c6574f3feaf2203b5671db1907a1e15c653:
> >
> >   drm/i915: Reinstate the mmap ioctl for some platforms (2021-06-28 07:43:56 -0400)
> >
> > ----------------------------------------------------------------
> > The biggest fix is the restoration of mmap ioctl for gen12 integrated parts
> > which lack was breaking ADL-P with media stack.
> > Besides that a small selftest fix and a theoretical overflow on
> > i915->pipe_to_crtc_mapping.
> >
> > ----------------------------------------------------------------
> > Chris Wilson (1):
> >       drm/i915/selftests: Reorder tasklet_disable vs local_bh_disable
> >
> > Jani Nikula (1):
> >       drm/i915/dsc: abstract helpers to get bigjoiner primary/secondary crtc
> >
> > Thomas Hellström (1):
> >       drm/i915: Reinstate the mmap ioctl for some platforms
> >
> >  drivers/gpu/drm/i915/display/intel_display.c       |  7 ++-
> >  drivers/gpu/drm/i915/display/intel_display_types.h |  8 ++++
> >  drivers/gpu/drm/i915/display/intel_vdsc.c          | 40 +++++++++++-----
> >  drivers/gpu/drm/i915/display/intel_vdsc.h          |  1 +
> >  drivers/gpu/drm/i915/gem/i915_gem_mman.c           |  7 +--
> >  drivers/gpu/drm/i915/gt/selftest_execlists.c       | 55 +++++++++++++---------
> >  6 files changed, 76 insertions(+), 42 deletions(-)
> 
> -- 
> Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2021-06-30 19:05 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29 18:54 [Intel-gfx] [PULL] drm-intel-next-fixes Rodrigo Vivi
2021-06-29 18:54 ` Rodrigo Vivi
2021-06-30 10:05 ` [Intel-gfx] " Jani Nikula
2021-06-30 10:05   ` Jani Nikula
2021-06-30 19:04   ` Rodrigo Vivi [this message]
2021-06-30 19:04     ` Rodrigo Vivi
2021-07-01  8:57     ` [Intel-gfx] " Jani Nikula
2021-07-01  8:57       ` Jani Nikula
2021-07-01 19:30       ` [Intel-gfx] " Rodrigo Vivi
2021-07-01 19:30         ` Rodrigo Vivi
  -- strict thread matches above, loose matches on Subject: below --
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-08-05  8:46 ` Mauro Carvalho Chehab
2022-08-05  8:46   ` Mauro Carvalho Chehab
2022-08-05 14:39   ` Rodrigo Vivi
2022-08-05 14:39     ` Rodrigo Vivi
2022-08-05 15:25     ` Mauro Carvalho Chehab
2022-08-05 15:25       ` Mauro Carvalho Chehab
2022-08-05 20:39       ` Rodrigo Vivi
2022-08-05 20:39         ` 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-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-28 14:15 ` Joonas Lahtinen
2019-11-22 15:55 Joonas Lahtinen
2019-11-22 15:55 ` Joonas Lahtinen
2019-11-20 20:40 Joonas Lahtinen
2019-11-20 20:40 ` Joonas Lahtinen
2019-11-22 12:08   ` Joonas Lahtinen
2019-11-22 12:08     ` Joonas Lahtinen
2019-11-14  8:52 Joonas Lahtinen
2019-11-14  8:52 ` Joonas Lahtinen
2019-11-07 14:50 Joonas Lahtinen
2019-11-07 14:50 ` Joonas Lahtinen

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=YNzAViVC1l4hE/uG@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=airlied@gmail.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=jani.nikula@linux.intel.com \
    --cc=mripard@kernel.org \
    /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.