All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the tty tree
Date: Tue, 10 Mar 2015 10:19:04 +0100	[thread overview]
Message-ID: <20150310091904.GB13728@kroah.com> (raw)
In-Reply-To: <20150310082318.GH7525@pengutronix.de>

On Tue, Mar 10, 2015 at 09:23:18AM +0100, Uwe Kleine-König wrote:
> Hello Greg,
> 
> On Tue, Mar 10, 2015 at 04:28:16PM +1100, Stephen Rothwell wrote:
> > After merging the tty tree, today's linux-next build (arm
> > multi_v7_defconfig) produced this warning:
> > 
> > drivers/tty/serial/imx.c: In function 'imx_set_termios':
> > drivers/tty/serial/imx.c:1301:7: warning: suggest explicit braces to avoid ambiguous 'else' [-Wparentheses]
> >     if (port->rs485.flags & SER_RS485_ENABLED)
> >        ^
> > 
> > Introduced by commit 17b8f2a3fdca ("serial: imx: add support for half
> > duplex rs485").
> should I send a fixed commit or do you prefer an incremental change?

It's already in my tree, so I need an add-on patch.

thanks,

greg k-h

  reply	other threads:[~2015-03-10  9:19 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10  5:28 linux-next: build warning after merge of the tty tree Stephen Rothwell
2015-03-10  8:23 ` Uwe Kleine-König
2015-03-10  9:19   ` Greg KH [this message]
2015-03-10  8:31 ` [PATCH] fixup! serial: imx: add support for half duplex rs485 Uwe Kleine-König
2015-03-10  9:19   ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2022-11-07  3:34 linux-next: build warning after merge of the tty tree Stephen Rothwell
2022-11-07  3:47 ` Kees Cook
2022-04-20  6:32 Stephen Rothwell
2022-04-19  6:33 Stephen Rothwell
2022-04-19  6:35 ` Stephen Rothwell
2022-04-19  6:36   ` Jiri Slaby
2022-04-19  6:35 ` Jiri Slaby
2020-09-29  6:01 Stephen Rothwell
2020-09-29  6:41 ` miaoqinglang
2020-09-29  7:32   ` Greg KH
2020-09-29  8:58     ` miaoqinglang
2020-09-09  5:56 Stephen Rothwell
2020-09-09  7:41 ` Greg KH
2018-09-19  3:12 Stephen Rothwell
2018-07-23  5:39 Stephen Rothwell
2018-07-23  9:03 ` Andy Shevchenko
2017-02-06  4:16 Stephen Rothwell
2017-02-06  8:50 ` Greg KH
2017-02-06 17:01   ` Ulrich Hecht
2017-02-06 22:37     ` Stephen Rothwell
2017-02-07  8:37       ` Greg KH
2017-02-07 11:18         ` Stephen Rothwell
2016-01-21  1:56 Stephen Rothwell
2016-01-21  2:07 ` Greg KH
2010-09-24  4:03 Stephen Rothwell
2010-09-24  4:44 ` Greg KH

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=20150310091904.GB13728@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=u.kleine-koenig@pengutronix.de \
    /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.