From: Jani Nikula <jani.nikula@linux.intel.com>
To: Nicholas Piggin <npiggin@gmail.com>,
Chris Wilson <chris@chris-wilson.co.uk>
Cc: linux-kbuild@vger.kernel.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] drm/i915: select CRC32
Date: Wed, 28 Jun 2017 11:53:02 +0300 [thread overview]
Message-ID: <87a84scx3l.fsf@intel.com> (raw)
In-Reply-To: <20170621192636.6fdba5cf@roar.ozlabs.ibm.com>
On Wed, 21 Jun 2017, Nicholas Piggin <npiggin@gmail.com> wrote:
> On Wed, 21 Jun 2017 10:15:56 +0100
> Chris Wilson <chris@chris-wilson.co.uk> wrote:
>
>> Quoting Daniel Vetter (2017-06-21 10:13:41)
>> > On Wed, Jun 21, 2017 at 04:34:20PM +1000, Nicholas Piggin wrote:
>> > > kbuild test robot found a build failure when building with thin
>> > > archives:
>> > >
>> > > http://marc.info/?l=linux-kbuild&m=149802285009737&w=2
>> > >
>> > > Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
>> >
>> > Pushed to drm-intel for 4.14, thanks.
>>
>> Probably deserves to be in fixes if we identify what introduced the CRC
>> dep. mst-dp? pipe crc?
>
> Looks like
>
> 579cea5f3 ("drm/i915/gvt: golden virtual HW state management")
Thus the select should've been under DRM_I915_GVT.
BR,
Jani.
>
> Thanks,
> Nick
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Jani Nikula, Intel Open Source Technology Center
prev parent reply other threads:[~2017-06-28 8:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 6:34 [PATCH] drm/i915: select CRC32 Nicholas Piggin
2017-06-21 9:13 ` Daniel Vetter
2017-06-21 9:15 ` Chris Wilson
2017-06-21 9:15 ` Chris Wilson
2017-06-21 9:26 ` Nicholas Piggin
2017-06-28 8:53 ` Jani Nikula [this message]
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=87a84scx3l.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=yamada.masahiro@socionext.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.