From: Alexandre Torgue <alexandre.torgue@st.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial: SERIAL_STM32 should depend on HAS_DMA
Date: Thu, 6 Oct 2016 16:08:21 +0200 [thread overview]
Message-ID: <b679c594-d16b-3339-3606-e152107053e0@st.com> (raw)
In-Reply-To: <1475762124-16609-1-git-send-email-geert@linux-m68k.org>
Hi Geert,
On 10/06/2016 03:55 PM, Geert Uytterhoeven wrote:
> If NO_DMA=y:
>
> drivers/built-in.o: In function `stm32_serial_remove':
> stm32-usart.c:(.text+0xcea1a): undefined reference to `bad_dma_ops'
> stm32-usart.c:(.text+0xcea7a): undefined reference to `bad_dma_ops'
>
> Add a dependency on HAS_DMA to fix this.
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> ---
> drivers/tty/serial/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/tty/serial/Kconfig b/drivers/tty/serial/Kconfig
> index c7831407a882d2bb..25c1d7bc010043b1 100644
> --- a/drivers/tty/serial/Kconfig
> +++ b/drivers/tty/serial/Kconfig
> @@ -1625,6 +1625,7 @@ config SERIAL_SPRD_CONSOLE
> config SERIAL_STM32
> tristate "STMicroelectronics STM32 serial port support"
> select SERIAL_CORE
> + depends on HAS_DMA
> depends on ARM || COMPILE_TEST
> help
> This driver is for the on-chip Serial Controller on
>
I sent same kind of patch this morning (but mine have a bad copy paste).
I will abandon my patch.
However for this one:
Acked-by: Alexandre Torgue <alexandre.torgue@st.com>
regards
Alex
prev parent reply other threads:[~2016-10-06 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 13:55 [PATCH] serial: SERIAL_STM32 should depend on HAS_DMA Geert Uytterhoeven
2016-10-06 14:08 ` Alexandre Torgue [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=b679c594-d16b-3339-3606-e152107053e0@st.com \
--to=alexandre.torgue@st.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
/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