From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Cc: "dim-tools@lists.freedesktop.org"
<dim-tools@lists.freedesktop.org>,
"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"mripard@kernel.org" <mripard@kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
"airlied@gmail.com" <airlied@gmail.com>
Subject: Re: [Intel-gfx] [PULL] drm-intel-next
Date: Wed, 2 Nov 2022 07:29:41 +0200 [thread overview]
Message-ID: <Y2IARZ1YTK4f3wJE@intel.com> (raw)
In-Reply-To: <d97f246025eefa859708b1923a81bd15a9fda179.camel@intel.com>
On Tue, Nov 01, 2022 at 10:29:24PM +0000, Vivi, Rodrigo wrote:
> On Sat, 2022-10-29 at 02:41 +0300, Ville Syrjälä wrote:
> > On Fri, Oct 28, 2022 at 02:22:33PM -0400, Rodrigo Vivi wrote:
> > > Hi Dave and Daniel,
> > >
> > > Here goes the first chunk of drm-intel-next targeting 6.2
> > >
> > > The highlight goes to Ville with many display related clean-up
> > > and improvement, some other MTL enabling work and many other
> > > fixes and small clean-ups.
> > >
> > > drm-intel-next-2022-10-28:
> > ...
> > > - ELD precompute and readout (Ville)
> >
> > A slight clarification seems to be in order. The ELD
> > precompute+readout is in fact not in yet. This was just a pile
> > of cleanups and minor fixes. The real ELD stuff will come later,
> > once we figure out how we actually want to do it.
>
> Sorry for the confusion. I have just used the subject of your series
> as summary:
> [Intel-gfx] [PATCH 00/22] drm/i915: ELD precompute and readout
Only part of the series went in.
>
> Should I change that to ELD precompute and readout
Just "audio cleanups" or something like that would be the
approximate truth.
--
Ville Syrjälä
Intel
WARNING: multiple messages have this Message-ID (diff)
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Cc: "dim-tools@lists.freedesktop.org"
<dim-tools@lists.freedesktop.org>,
"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"tzimmermann@suse.de" <tzimmermann@suse.de>
Subject: Re: [Intel-gfx] [PULL] drm-intel-next
Date: Wed, 2 Nov 2022 07:29:41 +0200 [thread overview]
Message-ID: <Y2IARZ1YTK4f3wJE@intel.com> (raw)
In-Reply-To: <d97f246025eefa859708b1923a81bd15a9fda179.camel@intel.com>
On Tue, Nov 01, 2022 at 10:29:24PM +0000, Vivi, Rodrigo wrote:
> On Sat, 2022-10-29 at 02:41 +0300, Ville Syrjälä wrote:
> > On Fri, Oct 28, 2022 at 02:22:33PM -0400, Rodrigo Vivi wrote:
> > > Hi Dave and Daniel,
> > >
> > > Here goes the first chunk of drm-intel-next targeting 6.2
> > >
> > > The highlight goes to Ville with many display related clean-up
> > > and improvement, some other MTL enabling work and many other
> > > fixes and small clean-ups.
> > >
> > > drm-intel-next-2022-10-28:
> > ...
> > > - ELD precompute and readout (Ville)
> >
> > A slight clarification seems to be in order. The ELD
> > precompute+readout is in fact not in yet. This was just a pile
> > of cleanups and minor fixes. The real ELD stuff will come later,
> > once we figure out how we actually want to do it.
>
> Sorry for the confusion. I have just used the subject of your series
> as summary:
> [Intel-gfx] [PATCH 00/22] drm/i915: ELD precompute and readout
Only part of the series went in.
>
> Should I change that to ELD precompute and readout
Just "audio cleanups" or something like that would be the
approximate truth.
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2022-11-02 5:29 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 18:22 [Intel-gfx] [PULL] drm-intel-next Rodrigo Vivi
2022-10-28 18:22 ` Rodrigo Vivi
2022-10-28 23:41 ` [Intel-gfx] " Ville Syrjälä
2022-10-28 23:41 ` Ville Syrjälä
2022-11-01 22:29 ` Vivi, Rodrigo
2022-11-01 22:29 ` Vivi, Rodrigo
2022-11-02 5:29 ` Ville Syrjälä [this message]
2022-11-02 5:29 ` Ville Syrjälä
-- strict thread matches above, loose matches on Subject: below --
2023-11-23 19:03 Jani Nikula
2023-11-23 19:39 ` Daniel Vetter
2023-10-19 16:18 Rodrigo Vivi
2023-10-12 13:42 Jani Nikula
2023-09-29 10:49 Jani Nikula
2023-08-10 19:53 Rodrigo Vivi
2023-08-03 18:56 Rodrigo Vivi
2023-06-05 14:20 Jani Nikula
2023-04-06 14:03 Rodrigo Vivi
2023-04-06 16:24 ` Daniel Vetter
2023-03-23 20:43 Rodrigo Vivi
2023-03-24 20:13 ` Daniel Vetter
2023-03-07 22:00 Rodrigo Vivi
2023-03-08 13:24 ` Rodrigo Vivi
2023-03-08 13:24 ` Rodrigo Vivi
2023-01-27 11:11 Jani Nikula
2023-01-12 12:06 Jani Nikula
2022-11-18 21:40 Rodrigo Vivi
2022-09-16 12:09 Jani Nikula
2022-08-29 13:22 Jani Nikula
2022-09-15 11:55 ` Jani Nikula
2022-07-07 3:04 Rodrigo Vivi
2022-06-22 19:53 Rodrigo Vivi
2022-05-06 10:47 Jani Nikula
2022-04-13 15:51 Jani Nikula
2022-02-23 23:29 Rodrigo Vivi
2022-02-08 14:58 Rodrigo Vivi
2021-12-14 15:37 Jani Nikula
2021-11-30 15:04 Jani Nikula
2021-10-15 18:45 Rodrigo Vivi
2021-10-04 19:01 Rodrigo Vivi
2021-08-10 13:51 Jani Nikula
2021-06-09 21:30 Rodrigo Vivi
2021-05-19 19:10 Rodrigo Vivi
2021-04-01 9:06 Jani Nikula
2021-03-16 16:24 Jani Nikula
2021-01-29 22:53 Rodrigo Vivi
2021-01-27 14:08 Rodrigo Vivi
2021-01-27 21:51 ` Ville Syrjälä
2021-01-12 17:51 Rodrigo Vivi
2021-01-04 21:10 Rodrigo Vivi
2021-01-07 12:02 ` Daniel Vetter
2020-09-18 17:30 Rodrigo Vivi
2020-08-26 23:27 Rodrigo Vivi
2020-07-15 13:19 Jani Nikula
2020-07-15 13:33 ` Jani Nikula
2020-07-15 14:05 ` Daniel Vetter
2020-07-02 18:29 Jani Nikula
2020-05-15 16:07 Joonas Lahtinen
2020-04-30 12:49 Joonas Lahtinen
2020-05-13 17:10 ` Joonas Lahtinen
2020-05-14 1:28 ` Dave Airlie
2020-05-14 14:55 ` Joonas Lahtinen
2020-04-17 11:15 Joonas Lahtinen
2020-02-25 18:58 Rodrigo Vivi
2020-01-14 11:43 Jani Nikula
2020-01-14 12:05 ` Chris Wilson
2020-01-14 12:15 ` Jani Nikula
2019-12-23 17:53 Jani Nikula
2019-11-01 10:47 Joonas Lahtinen
2019-11-01 10:47 ` Joonas Lahtinen
2015-12-22 10:37 Daniel Vetter
2015-12-22 14:05 ` Daniel Vetter
2015-12-22 14:31 ` Chris Wilson
2015-12-22 16:31 ` [Intel-gfx] " Tvrtko Ursulin
2015-12-23 10:09 ` Chris Wilson
2014-04-28 13:26 Daniel Vetter
2014-05-06 13:08 ` [Intel-gfx] " Knut Petersen
2014-05-06 13:30 ` Jani Nikula
2014-05-06 18:59 ` Daniel Vetter
2014-05-06 20:04 ` Knut Petersen
2014-05-06 20:17 ` [Intel-gfx] " Daniel Vetter
2012-09-13 14:18 [pull] drm-intel-next Daniel Vetter
2012-09-14 13:55 ` [Intel-gfx] " Bobby Powers
2012-09-14 15:43 ` Daniel Vetter
2012-09-14 19:52 ` Paulo Zanoni
2012-01-05 3:35 [PULL] drm-intel-next Keith Packard
2012-01-05 15:24 ` Daniel Vetter
2012-01-05 17:58 ` [Intel-gfx] " Ben Widawsky
2012-01-05 18:02 ` Jesse Barnes
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=Y2IARZ1YTK4f3wJE@intel.com \
--to=ville.syrjala@linux.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=mripard@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=tzimmermann@suse.de \
/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.