From: Lee Jones <lee.jones@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
robdclark@gmail.com
Subject: Re: linux-next: strange commit in the mfd tree
Date: Thu, 22 Jan 2015 07:53:28 +0000 [thread overview]
Message-ID: <20150122075328.GN22024@x1> (raw)
In-Reply-To: <20150122095638.46a0b503@canb.auug.org.au>
On Thu, 22 Jan 2015, Stephen Rothwell wrote:
> Hi Lee,
>
> I noticed this commit in the mfd tree:
>
> f11b9265e6ca "[FIX/HACK] Disable DRM"
>
> Is that really appropriate here? Especially given it has no explanation.
>
> I guess it will make my builds slightly faster :-)
You're right, this is an escapee. It should have been removed
post-testing. I have asked Rob Clark to take a look at the issue it
'solves'. FYI, arm,multi_v7 fails to build with raised warning levels
>=1.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2015-01-22 7:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 22:56 linux-next: strange commit in the mfd tree Stephen Rothwell
2015-01-22 7:53 ` Lee Jones [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=20150122075328.GN22024@x1 \
--to=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox