linux-kernel - Re: [GIT PULL 3/3] bcm2835-arm64-next-2016-07-03

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <577C8022.9000600@gmail.com>
Date:	Tue, 5 Jul 2016 20:50:58 -0700
From:	Florian Fainelli <f.fainelli@...il.com>
To:	Jason Cooper <jason@...edaemon.net>, Eric Anholt <eric@...olt.net>
Cc:	linux-rpi-kernel@...ts.infradead.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Stephen Warren <swarren@...dotorg.org>,
	Lee Jones <lee@...nel.org>
Subject: Re: [GIT PULL 3/3] bcm2835-arm64-next-2016-07-03

Le 05/07/2016 11:03, Jason Cooper a écrit :
> Eric,
> 
> On Sun, Jul 03, 2016 at 05:45:36PM -0700, Eric Anholt wrote:
>>   Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
>>
>> are available in the git repository at:
>>
>>   https://github.com/anholt/linux tags/bcm2835-arm64-next-2016-07-03
>>
>> for you to fetch changes up to 628d30d1ccb897fee54a6f7312561cf2f6f72f09:
>>
>>   arm64: Add platform selection for BCM2835. (2016-06-15 14:10:30 -0700)
>>
>> ----------------------------------------------------------------
>> This pull request brings in the build support for the Raspberry Pi
>> arm64 port.
>>
>> ----------------------------------------------------------------
>> Alexander Graf (1):
>>       arm64: Allow for different DMA and CPU bus offsets
>>
>> Eric Anholt (3):
>>       irqchip: bcm2835: Avoid arch/arm-specific handle_IRQ
>>       Merge remote-tracking branch 'irqchip/irqchip/bcm' into bcm2835-arm64-next
> 
> You may want to draw attention to the fact that this has an external
> dependency on my irqchip/bcm branch.  Also, that it's stable, been in
> -next for a couple of weeks, and based on v4.7-rc1, etc.

Thanks for the heads-up, merged and updated the merge commit to make
this clear, thanks everyone.
-- 
Florian