From: David Weinehall <david.weinehall@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2 v2] drm/i915: Allow parsing of variable size child device entries from VBT
Date: Thu, 6 Aug 2015 17:12:17 +0300 [thread overview]
Message-ID: <20150806141217.GG6150@boom> (raw)
In-Reply-To: <20150806121835.GE17734@phenom.ffwll.local>
On Thu, Aug 06, 2015 at 02:18:35PM +0200, Daniel Vetter wrote:
> On Wed, Aug 05, 2015 at 06:32:01PM +0300, David Weinehall wrote:
> > On Wed, Aug 05, 2015 at 10:59:00AM +0200, Daniel Vetter wrote:
> > > On Tue, Aug 04, 2015 at 04:55:52PM +0300, David Weinehall wrote:
> > > > VBT version 196 increased the size of common_child_dev_config. The parser
> > > > code assumed that the size of this structure would not change.
> > > >
> > > > The modified code now copies the amount needed based on the VBT version,
> > > > and emits a debug message if the VBT version is unknown (too new);
> > > > since the struct config block won't shrink in newer versions it should
> > > > be harmless to copy the maximum known size in such cases, so that's
> > > > what we do, but emitting the warning is probably sensible anyway.
> > > >
> > > > In the longer run it might make sense to modify the parser code to
> > > > use a version/feature mapping, rather than hardcoding things like this,
> > > > but for now the variants are fairly managable.
> > > >
> > > > v2: Stricter size checks
> > > >
> > > > Signed-off-by: David Weinehall <david.weinehall@linux.intel.com>
> > >
> > > Since Chris mentioned that this should fix a regression I applied it to
> > > drm-intel-fixes.
> >
> > Great! Will you merge the other patch in the series to the nightly
> > build?
>
> I only merged this fast-tracked because it fixes a regression. For the
> other patch normal review rules still apply (i.e. I won't do it).
I wasn't expecting fast tracking. I'd missed the fact that patch 2/2
wasn't reviewed by anyone yet; I've done so now.
Kind regards, David
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-08-06 14:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 11:10 [PATCH 0/2] VBT and I_boost fixes Antti Koskipaa
2015-07-10 11:10 ` [PATCH 1/2] drm/i915: Allow parsing of variable size child device entries from VBT Antti Koskipaa
2015-07-10 12:32 ` David Weinehall
2015-07-13 9:24 ` Daniel Vetter
2015-07-14 7:11 ` David Weinehall
2015-07-14 8:01 ` Daniel Vetter
2015-08-04 13:55 ` [PATCH 1/2 v2] " David Weinehall
2015-08-05 8:59 ` Daniel Vetter
2015-08-05 15:32 ` David Weinehall
2015-08-06 12:18 ` Daniel Vetter
2015-08-06 14:12 ` David Weinehall [this message]
2015-08-06 13:59 ` Michel Thierry
2015-08-06 14:08 ` David Weinehall
2015-08-06 15:31 ` Daniel Vetter
2015-08-12 10:29 ` [PATCH 1/2 v2 addendum] " David Weinehall
2015-08-12 12:13 ` Jani Nikula
2015-08-13 10:30 ` David Weinehall
2015-08-13 11:35 ` Jani Nikula
2015-08-12 14:19 ` Jani Nikula
2015-08-13 13:14 ` [PATCH 1/2 v2 addendum v2] " David Weinehall
2015-08-14 8:07 ` Timo Aaltonen
2015-08-14 8:42 ` Jani Nikula
2015-08-14 9:40 ` Jani Nikula
2015-07-10 11:10 ` [PATCH 2/2] drm/i915: Per-DDI I_boost override Antti Koskipaa
2015-08-06 14:11 ` David Weinehall
2015-08-06 15:31 ` 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=20150806141217.GG6150@boom \
--to=david.weinehall@linux.intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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.