All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	John Stultz <john.stultz@linaro.org>
Subject: Re: linux-next: build failure after merge of the staging.current tree
Date: Thu, 14 Dec 2017 08:27:30 +0100	[thread overview]
Message-ID: <20171214072730.GD27027@kroah.com> (raw)
In-Reply-To: <20171214170033.24a606b6@canb.auug.org.au>

On Thu, Dec 14, 2017 at 05:00:33PM +1100, Stephen Rothwell wrote:
> Hi Greg,
> 
> After merging the staging.current tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
> 
> drivers/staging/android/ion/ion_cma_heap.c: In function 'ion_cma_allocate':
> drivers/staging/android/ion/ion_cma_heap.c:38:14: error: 'CONFIG_CMA_ALIGNMENT' undeclared (first use in this function)
>   if (align > CONFIG_CMA_ALIGNMENT)
>               ^
> 
> Caused by commit
> 
>   d98e6dbf42f7 ("staging: ion: Fix ion_cma_heap allocations")
> 
> CONFIG_CMA_ALIGNMENT (and CONFIG_DMA_CMA) is not set for this build.
> 
> I have reverted that commit for today.

Thanks, and sorry about that.  John is working on a fix...

greg k-h

  reply	other threads:[~2017-12-14  7:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14  6:00 linux-next: build failure after merge of the staging.current tree Stephen Rothwell
2017-12-14  7:27 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-08 10:42 Stephen Rothwell
2025-01-08 11:48 ` Greg KH
2011-06-08  1:41 Stephen Rothwell
2011-06-08 16:11 ` Greg KH
2011-06-08 16:58   ` Mauro Carvalho Chehab
2011-06-08 16:21 ` Greg KH

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=20171214072730.GD27027@kroah.com \
    --to=greg@kroah.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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 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.