All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linaro-kernel@lists.linaro.org
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>,
	Dave Airlie <airlied@redhat.com>,
	kernel-build-reports@lists.linaro.org,
	dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: v4.7-rc2 build: 0 failures 5 warnings (v4.7-rc2)
Date: Mon, 06 Jun 2016 11:44:33 +0200	[thread overview]
Message-ID: <4062856.1Bu0ArSlWE@wuerfel> (raw)
In-Reply-To: <E1b9j2R-0002zq-R2@optimist>

On Monday, June 6, 2016 2:09:07 AM CEST Build bot for Mark Brown wrote:
> arm-allmodconfig : PASS, 0 errors, 2 warnings, 0 section mismatches
> 
> Warnings:
>         ../drivers/gpu/drm/omapdrm/dss/dsi.c:1170:6: warning: unused variable 'r' [-Wunused-variable]
>         ../drivers/gpu/drm/omapdrm/dss/hdmi5.c:123:6: warning: unused variable 'r' [-Wunused-variable]

These got introduced by Fixes: 973999aa0140 ("drm/omap: Remove
regulator API abuse") in 4.7-rc2, and are trivial to fix, I can provide a
patch if needed.

I also have a couple of other regression fixes in my local tree 
that I hope to see in 4.7, but with DRM I never know when to resend
them, as they sometimes do not show up in linux-next before they get
merged into mainline.

This is my current backlog:

d703eb3c7606 [IN NEXT] drm: sun4i: fix probe error handling
ee0d3dafedb7 [IN NEXT] drm: sun4i: print DMA address correctly
4b51817edcd0 [IN NEXT] drm/sun4i: add COMMON_CLK dependency
04197e0d8201 [SUBMITTED 20160516] drm: exynos: mark pm functions as __maybe_unused
1aa3f513d264 [SUBMITTED 20160516] drm: mediatek: add CONFIG_OF dependency
dee4d1c31214 [SUBMITTED 20160511] drm: mediatek: remove IOMMU_DMA select
845cd86005ea [SUBMITTED 20160511] drm/omap: include linux/of.h where needed
d657e5dd56c5 [SUBMITTED 20160511] drm: mediatek: add COMMON_CLK dependency
539c2a57be6f [SUBMITTED x2 20160225] drm: avoid uninitialized timestamp use in wait_vblank
921b0acae44c [SUBMITTED 2015012drm: armada: use dma_addr_t properly

Am I right to assume that as the first eight that are all regressions against
4.6 will show up in 4.7 without me doing anything further, but that I should
resend the last two so they can make it into 4.8, and get backported if
necessary?

	Arnd
_______________________________________________
Kernel-build-reports mailing list
Kernel-build-reports@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/kernel-build-reports

       reply	other threads:[~2016-06-06  9:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1b9j2R-0002zq-R2@optimist>
2016-06-06  9:44 ` Arnd Bergmann [this message]
2016-06-06 10:08   ` v4.7-rc2 build: 0 failures 5 warnings (v4.7-rc2) Peter Ujfalusi
2016-06-06 10:13     ` Tomi Valkeinen
2016-06-06 10:29       ` Arnd Bergmann

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=4062856.1Bu0ArSlWE@wuerfel \
    --to=arnd@arndb.de \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.ujfalusi@ti.com \
    --cc=tomi.valkeinen@ti.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.