From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Gerald Baeza <gerald.baeza@st.com>,
linux-pwm@vger.kernel.org
Subject: Re: linux-next: Tree for May 17 (drivers/pwm/pwm-stm32.c)
Date: Thu, 17 May 2018 11:34:59 -0700 [thread overview]
Message-ID: <b611bea0-d77b-7841-2127-277acda55747@infradead.org> (raw)
In-Reply-To: <20180517170656.1f746914@canb.auug.org.au>
On 05/17/2018 12:06 AM, Stephen Rothwell wrote:
> Hi all,
>
on x86_64:
drivers/pwm/pwm-stm32.o: In function `stm32_pwm_raw_capture':
pwm-stm32.c:(.text+0x53d): undefined reference to `stm32_timers_dma_burst_read'
when COMPILE_TEST=y and MFD_STM32_TIMERS is not set.
Any suggestions?
thanks,
--
~Randy
next prev parent reply other threads:[~2018-05-17 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 7:06 linux-next: Tree for May 17 Stephen Rothwell
2018-05-17 16:55 ` linux-next: Tree for May 17 (usb/gadget/udc/aspeed-vhub/) Randy Dunlap
2018-05-17 18:03 ` linux-next: Tree for May 17 Naresh Kamboju
2018-05-17 18:34 ` Randy Dunlap [this message]
2018-05-22 14:18 ` Mark Brown
2018-05-23 23:07 ` Mark Brown
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=b611bea0-d77b-7841-2127-277acda55747@infradead.org \
--to=rdunlap@infradead.org \
--cc=gerald.baeza@st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pwm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).