linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Boris Brezillon <boris.brezillon@free-electrons.com>,
	Nicolas Ferre <nicolas.ferre@atmel.com>
Subject: Re: linux-next: Tree for Jan 23
Date: Fri, 23 Jan 2015 10:34:44 -0800	[thread overview]
Message-ID: <20150123183444.GA337@roeck-us.net> (raw)
In-Reply-To: <20150123181029.35e688d1@canb.auug.org.au>

On Fri, Jan 23, 2015 at 06:10:29PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> There will be no linux-next release on Monday (next-20150126).
> 
> Changes since 20150122:
> 
> Added tree:	kvms390
> Removed tree:	documentation (at maintainers request)
> 
> The vfs tree gained a conflict against Linus' tree.
> 
> The akpm tree lost a patch that turned up elsewhere.
> 
> Non-merge commits (relative to Linus' tree): 4500
>  4390 files changed, 174556 insertions(+), 78123 deletions(-)
> 
> ----------------------------------------------------------------------------
> 
xtensa:allmodconfig fails with:

drivers/gpu/drm/drm_gem_cma_helper.c: In function ‘drm_gem_cma_create’:
drivers/gpu/drm/drm_gem_cma_helper.c:110:2: error: implicit declaration of
function ‘dma_alloc_writecombine’ [-Werror=implicit-function-declaration]
drivers/gpu/drm/drm_gem_cma_helper.c:110:17: warning: assignment makes pointer
from integer without a cast [enabled by default]
drivers/gpu/drm/drm_gem_cma_helper.c: In function ‘drm_gem_cma_free_object’:
drivers/gpu/drm/drm_gem_cma_helper.c:193:3: error: implicit declaration of
function ‘dma_free_writecombine’ [-Werror=implicit-function-declaration]
drivers/gpu/drm/drm_gem_cma_helper.c: In function ‘drm_gem_cma_mmap_obj’:
drivers/gpu/drm/drm_gem_cma_helper.c:330:2: error: implicit declaration of
function ‘dma_mmap_writecombine’ [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[3]: *** [drivers/gpu/drm/drm_gem_cma_helper.o] Error 1

Ultimately caused by 'drm: add Atmel HLCDC Display Controller support',
which selects DRM_GEM_CMA_HELPER.
DRM_ATMEL_HLCDC seems to be missing some dependencies, or possibly
DRM_GEM_CMA_HELPER (and/or every driver selecting it) needs to depend
on HAVE_DMA_ATTRS.

Ultimately this may result in allmodconfig/allyesconfig build failures
on all architectures which don't define HAVE_DMA_ATTRS.

Guenter

  reply	other threads:[~2015-01-23 18:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23  7:10 linux-next: Tree for Jan 23 Stephen Rothwell
2015-01-23 18:34 ` Guenter Roeck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-23  5:57 Stephen Rothwell
2024-01-23  2:29 Stephen Rothwell
2023-01-23  4:31 Stephen Rothwell
2020-01-23  6:21 Stephen Rothwell
2019-01-23  5:24 Stephen Rothwell
2017-01-23  5:08 Stephen Rothwell
2014-01-23  6:21 Stephen Rothwell
2014-01-23  6:38 ` Stephen Rothwell
2014-01-23 14:44   ` Paul Gortmaker
2013-01-23  6:43 Stephen Rothwell
2013-01-23 22:18 ` Stephen Rothwell
2012-01-23  3:11 Stephen Rothwell

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=20150123183444.GA337@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=boris.brezillon@free-electrons.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nicolas.ferre@atmel.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;
as well as URLs for NNTP newsgroup(s).