All of lore.kernel.org
 help / color / mirror / Atom feed
From: CK Hu <ck.hu@mediatek.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: <linaro-kernel@lists.linaro.org>, Dave Airlie <airlied@gmail.com>,
	<dri-devel@lists.freedesktop.org>,
	Mark Brown <broonie@kernel.org>, <linux-kernel@vger.kernel.org>,
	<kernel-build-reports@lists.linaro.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Bibby Hsieh <bibby.hsieh@mediatek.com>
Subject: Re: DRM: urgent v4.9-rc6 build regression: master build: 2 failures 1 warnings (v4.9-rc5-213-g961b708)
Date: Fri, 18 Nov 2016 00:46:06 +0800	[thread overview]
Message-ID: <1479401166.30632.14.camel@mtksdaap41> (raw)
In-Reply-To: <3081141.oCXXbHYFFj@wuerfel>

Hi, Arnd:

I've made a mistake that I've tried to build these patches on v4.9-rc1,
but I does not set CONFIG_DRM_MEDIATEK=y, therefore I didn't find out
these build fails. Now I fix the config problem, and I think I should
build these patches on latest kernel version even though patch's owner
test on old kernel version. I wish this flow would make things better.

It's ok that you just revert these two patches. I've fixed build fail
and will request pull later.

Regards,
CK

On Thu, 2016-11-17 at 16:24 +0100, Arnd Bergmann wrote:
> On Thursday, November 17, 2016 8:50:05 PM CET Dave Airlie wrote:
> > 
> > Arnd could you send a git pull with the two reverts, with my Acked-by on
> > it? I won't be in a place to do it for 8-9hrs.
> 
> I don't think it's that urgent, as long as we make sure it's fixed in the
> next -rc. I've sent out the reverts as patches with a little more information
> in the changelog: it turns out that they are actually broken on linux-next too,
> they had just not made it in there, and one of the two actually did build
> on older kernels.
> 
> I think what happened here is that the fixes were tested on a v4.4 kernel
> and blindly forward-ported. It probably makes sense to look at the
> entire series again in case another one of them is broken.
> 
> Philipp, Hu, Bibby, could one of you have another look?
> 
> 	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: CK Hu <ck.hu@mediatek.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linaro-kernel@lists.linaro.org,
	kernel-build-reports@lists.linaro.org,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Mark Brown <broonie@kernel.org>
Subject: Re: DRM: urgent v4.9-rc6 build regression: master build: 2 failures 1 warnings (v4.9-rc5-213-g961b708)
Date: Fri, 18 Nov 2016 00:46:06 +0800	[thread overview]
Message-ID: <1479401166.30632.14.camel@mtksdaap41> (raw)
In-Reply-To: <3081141.oCXXbHYFFj@wuerfel>

Hi, Arnd:

I've made a mistake that I've tried to build these patches on v4.9-rc1,
but I does not set CONFIG_DRM_MEDIATEK=y, therefore I didn't find out
these build fails. Now I fix the config problem, and I think I should
build these patches on latest kernel version even though patch's owner
test on old kernel version. I wish this flow would make things better.

It's ok that you just revert these two patches. I've fixed build fail
and will request pull later.

Regards,
CK

On Thu, 2016-11-17 at 16:24 +0100, Arnd Bergmann wrote:
> On Thursday, November 17, 2016 8:50:05 PM CET Dave Airlie wrote:
> > 
> > Arnd could you send a git pull with the two reverts, with my Acked-by on
> > it? I won't be in a place to do it for 8-9hrs.
> 
> I don't think it's that urgent, as long as we make sure it's fixed in the
> next -rc. I've sent out the reverts as patches with a little more information
> in the changelog: it turns out that they are actually broken on linux-next too,
> they had just not made it in there, and one of the two actually did build
> on older kernels.
> 
> I think what happened here is that the fixes were tested on a v4.4 kernel
> and blindly forward-ported. It probably makes sense to look at the
> entire series again in case another one of them is broken.
> 
> Philipp, Hu, Bibby, could one of you have another look?
> 
> 	Arnd


_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-11-17 17:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1c7E60-0002LY-05@optimist>
2016-11-17 10:41 ` DRM: urgent v4.9-rc6 build regression: master build: 2 failures 1 warnings (v4.9-rc5-213-g961b708) Arnd Bergmann
2016-11-17 10:41   ` Arnd Bergmann
2016-11-17 10:50   ` Dave Airlie
2016-11-17 15:24     ` Arnd Bergmann
2016-11-17 15:24       ` Arnd Bergmann
2016-11-17 16:46       ` CK Hu [this message]
2016-11-17 16:46         ` CK Hu

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=1479401166.30632.14.camel@mtksdaap41 \
    --to=ck.hu@mediatek.com \
    --cc=airlied@gmail.com \
    --cc=arnd@arndb.de \
    --cc=bibby.hsieh@mediatek.com \
    --cc=broonie@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.zabel@pengutronix.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.