From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bich HEMON <bich.hemon@st.com>
Subject: Re: linux-next: build warnings after merge of the tty tree
Date: Thu, 15 Mar 2018 18:34:03 +0100 [thread overview]
Message-ID: <20180315173403.GA29986@kroah.com> (raw)
In-Reply-To: <20180315174331.6c7b600b@canb.auug.org.au>
On Thu, Mar 15, 2018 at 05:43:31PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> After merging the tty tree, today's linux-next build (arm
> multi_v7_defconfig) produced these warnings:
>
> drivers/tty/serial/stm32-usart.c:155:12: warning: 'stm32_init_rs485' defined but not used [-Wunused-function]
> static int stm32_init_rs485(struct uart_port *port,
> ^~~~~~~~~~~~~~~~
> drivers/tty/serial/stm32-usart.c:100:12: warning: 'stm32_config_rs485' defined but not used [-Wunused-function]
> static int stm32_config_rs485(struct uart_port *port,
> ^~~~~~~~~~~~~~~~~~
>
> Introduced by commit
>
> 1bcda09d2910 ("serial: stm32: add support for RS485 hardware control mode")
Fix for this just hit my tree, thanks for the notice.
greg k-h
next prev parent reply other threads:[~2018-03-15 17:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 6:43 linux-next: build warnings after merge of the tty tree Stephen Rothwell
2018-03-15 17:34 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-14 6:47 Stephen Rothwell
2022-05-10 21:58 Stephen Rothwell
2022-05-10 22:46 ` Maciej W. Rozycki
2022-05-11 5:32 ` Greg KH
2022-05-13 22:47 ` Maciej W. Rozycki
2015-03-10 5:37 Stephen Rothwell
2010-12-21 7:11 Stephen Rothwell
2010-12-21 19:42 ` Greg KH
2011-01-10 0:49 ` Stephen Rothwell
2011-01-10 0:51 ` Kay Sievers
2011-01-10 0:56 ` Greg KH
2011-01-10 1:59 ` Stephen Rothwell
2011-01-10 5:49 ` Greg KH
2011-01-10 14:55 ` Kay Sievers
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=20180315173403.GA29986@kroah.com \
--to=greg@kroah.com \
--cc=bich.hemon@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