From: Jan Kara <jack@suse•cz>
To: Mark Brown <broonie@kernel•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Paul Gortmaker <paul.gortmaker@windriver•com>,
kernel-build-reports@lists•linaro.org,
linaro-kernel@lists•linaro.org,
"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
jack@suse•cz, Andrew Morton <akpm@linux-foundation•org>,
Joonyoung Shim <jy0922.shim@samsung•com>,
Hans Verkuil <hans.verkuil@cisco•com>,
Mauro Carvalho Chehab <mchehab@osg•samsung.com>
Subject: Re: next-20150703 build: 1 failures 73 warnings (next-20150703)
Date: Wed, 8 Jul 2015 10:41:34 +0200 [thread overview]
Message-ID: <20150708084134.GD725@quack.suse.cz> (raw)
In-Reply-To: <20150705093654.GB11162@sirena.org.uk>
On Sun 05-07-15 10:36:54, Mark Brown wrote:
> On Sat, Jul 04, 2015 at 04:52:49PM +1000, Stephen Rothwell wrote:
> > On Sat, 4 Jul 2015 00:01:33 -0400 Paul Gortmaker <paul.gortmaker@windriver•com> wrote:
>
> > > 6e9d331aec60a3dd1bbc035fbdd84a90364b8565 is the first bad commit
> > > commit 6e9d331aec60a3dd1bbc035fbdd84a90364b8565
> > > Author: Jan Kara <jack@suse•cz>
> > > Date: Fri Jun 19 09:05:45 2015 +1000
>
> > > drm/exynos: convert g2d_userptr_get_dma_addr() to use get_vaddr_frames()
>
> > Amazing! Four SOB lines and lots of CCs and noone bothered to build test it :-(
>
> > > Fix seems posted here...
> > >
> > > http://permalink.gmane.org/gmane.comp.video.dri.devel/131898
>
> And there was another, similar fix sent as a result of me reporting the
> same issue earlier last week too with no response :(
There was another issue in the series due to which Andrew refreshed the
whole series in mm tree and this fix fell through the cracks. I should have
warned Andrew. Sorry, my fault.
Honza
--
Jan Kara <jack@suse•cz>
SUSE Labs, CR
prev parent reply other threads:[~2015-07-08 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 12:28 next-20150703 build: 1 failures 73 warnings (next-20150703) Build bot for Mark Brown
2015-07-04 4:01 ` Paul Gortmaker
2015-07-04 6:52 ` Stephen Rothwell
2015-07-05 9:36 ` Mark Brown
2015-07-08 8:41 ` Jan Kara [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=20150708084134.GD725@quack.suse.cz \
--to=jack@suse$(echo .)cz \
--cc=akpm@linux-foundation$(echo .)org \
--cc=broonie@kernel$(echo .)org \
--cc=hans.verkuil@cisco$(echo .)com \
--cc=jy0922.shim@samsung$(echo .)com \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mchehab@osg$(echo .)samsung.com \
--cc=paul.gortmaker@windriver$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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