| 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
| ||
|
Message-ID: <54EBBCBD.8000800@gentoo.org> Date: Mon, 23 Feb 2015 18:50:21 -0500 From: Joshua Kinard <kumba@...too.org> To: Randy Dunlap <rdunlap@...radead.org>, Stephen Rothwell <sfr@...b.auug.org.au>, linux-next@...r.kernel.org CC: linux-kernel@...r.kernel.org, Alessandro Zummo <a.zummo@...ertech.it> Subject: Re: linux-next: Tree for Feb 23 (rtc-ds1685) On 02/23/2015 13:36, Randy Dunlap wrote: > On 02/22/15 19:09, Stephen Rothwell wrote: >> Hi all, >> >> Please do not add any material destined for v3.21 to your linux-next >> included trees until after v3.20-rc1 has been released. >> >> OK, so that was interesting :-) v4.0-rc1 is out, so go crazy ... >> >> Changes since 20150222: >> >> *crickets* > > > for the last 4 days or so, I have been seeing this build error on > i386 and x86_64: > > ../drivers/rtc/rtc-ds1685.c:919:22: error: 'ds1685_rtc_alarm_irq_enable' undeclared here (not in a function) > .alarm_irq_enable = ds1685_rtc_alarm_irq_enable, > > when CONFIG_RTC_INTF_DEV is not enabled. A patch was sent upstream already for this: http://ozlabs.org/~akpm/mmots/broken-out/rtc-ds1685-fix-ds1685_rtc_alarm_irq_enable-build-error.patch I'm not sure when it will appear in linux-next (still new to this process). -- Joshua Kinard Gentoo/MIPS kumba@...too.org 4096R/D25D95E3 2011-03-28 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists