All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: stable <stable@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: v3.18-stable-queue and v4.1.y-stable-queue build failures
Date: Tue, 7 Jun 2016 06:33:42 -0700	[thread overview]
Message-ID: <5756CD36.8030501@roeck-us.net> (raw)
In-Reply-To: <57545831.9070106@oracle.com>

On 06/05/2016 09:49 AM, Sasha Levin wrote:
> On 06/04/2016 09:59 AM, Guenter Roeck wrote:
>> v3.18:
>>
>> arm64:defconfig:
>>
>> drivers/irqchip/irq-gic-v3.c: In function ‘gic_dist_init’:
>> drivers/irqchip/irq-gic-v3.c:319:29: error: ‘GICD_IGROUPR’
>>
>> drivers/irqchip/irq-gic-v3.c: In function ‘gic_cpu_init’:
>> drivers/irqchip/irq-gic-v3.c:417:29: error: ‘GICR_IGROUPR0’ undeclared
>>
>> All mips builds:
>>
>> arch/mips/kernel/setup.c: In function 'arch_mem_init':
>> arch/mips/kernel/setup.c:689:2: error: implicit declaration of function 'reserve_bootmem_region'
>>
>>
>> v4.1, all mips builds:
>>
>> arch/mips/mm/cache.c: In function '__update_cache':
>> arch/mips/mm/cache.c:134:26: error: implicit declaration of function 'kmap_atomic'
>> arch/mips/mm/cache.c:142:4: error: implicit declaration of function '__kunmap_atomic'
>>
>> arch/mips/kernel/setup.c: In function 'arch_mem_init':
>> arch/mips/kernel/setup.c:690:2: error: implicit declaration of function 'reserve_bootmem_region'
>>
>> Guenter
>
> Thanks Guenter, all should be fixed now.
>
Confirmed.

Can you let Greg know how you fixed the mips problem in mm/cache.c ? It now affects
4.4, 4.5, and 4.6 as well.

Thanks,
Guenter


  reply	other threads:[~2016-06-07 13:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-04 13:59 v3.18-stable-queue and v4.1.y-stable-queue build failures Guenter Roeck
2016-06-05 16:49 ` Sasha Levin
2016-06-07 13:33   ` Guenter Roeck [this message]
2016-06-07 16:46     ` Sasha Levin
2016-06-07 18:24       ` Guenter Roeck
2016-06-08  1:10         ` Greg Kroah-Hartman

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=5756CD36.8030501@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=sasha.levin@oracle.com \
    --cc=stable@vger.kernel.org \
    /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.