From: Joshua Kinard <kumba@gentoo.org>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Alessandro Zummo <a.zummo@towertech.it>
Subject: Re: linux-next: Tree for Feb 23 (rtc-ds1685)
Date: Mon, 23 Feb 2015 18:50:21 -0500 [thread overview]
Message-ID: <54EBBCBD.8000800@gentoo.org> (raw)
In-Reply-To: <54EB7328.5060704@infradead.org>
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@gentoo.org
4096R/D25D95E3 2011-03-28
prev parent reply other threads:[~2015-02-23 23:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 3:09 linux-next: Tree for Feb 23 Stephen Rothwell
2015-02-23 18:36 ` linux-next: Tree for Feb 23 (rtc-ds1685) Randy Dunlap
2015-02-23 23:50 ` Joshua Kinard [this message]
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=54EBBCBD.8000800@gentoo.org \
--to=kumba@gentoo.org \
--cc=a.zummo@towertech.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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.