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>,
Fabrice Gasnier <fabrice.gasnier@st.com>
Subject: Re: linux-next: Tree for Sep 7 (iio/adc/stm32)
Date: Thu, 7 Sep 2017 08:45:29 -0700 [thread overview]
Message-ID: <279c9bde-d174-e78a-407c-a9fd9aa6a0d5@infradead.org> (raw)
In-Reply-To: <20170907162457.0a04ae1e@canb.auug.org.au>
On 09/06/17 23:24, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v4.15 related material to your linux-next
> included branches until after v4.14-rc1 has been released.
>
> Changes since 20170906:
>
on i386:
CONFIG_STM32_ADC_CORE=y
CONFIG_STM32_ADC=y
CONFIG_IIO_STM32_LPTIMER_TRIGGER=m
CONFIG_IIO_STM32_TIMER_TRIGGER=y
causes:
drivers/iio/adc/stm32-adc.o: In function `stm32_adc_get_trig_extsel':
stm32-adc.c:(.text+0x9d6): undefined reference to `is_stm32_lptim_trigger'
due to builtin code trying to call code in a loadable module.
--
~Randy
prev parent reply other threads:[~2017-09-07 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 6:24 linux-next: Tree for Sep 7 Stephen Rothwell
2017-09-07 15:45 ` Randy Dunlap [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=279c9bde-d174-e78a-407c-a9fd9aa6a0d5@infradead.org \
--to=rdunlap@infradead.org \
--cc=fabrice.gasnier@st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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).