From: Greg KH <greg@kroah.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fixup! serial: imx: add support for half duplex rs485
Date: Tue, 10 Mar 2015 10:19:16 +0100 [thread overview]
Message-ID: <20150310091915.GC13728@kroah.com> (raw)
In-Reply-To: <1425976269-27169-1-git-send-email-u.kleine-koenig@pengutronix.de>
On Tue, Mar 10, 2015 at 09:31:09AM +0100, Uwe Kleine-König wrote:
> ---
> drivers/tty/serial/imx.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
Same errors as your other patch :(
prev parent reply other threads:[~2015-03-10 9:19 UTC|newest]
Thread overview: 5+ 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
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 [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=20150310091915.GC13728@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 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).