From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Soren Brinkmann <soren.brinkmann@xilinx.com>
Cc: Jiri Slaby <jslaby@suse.cz>,
Michal Simek <michal.simek@xilinx.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH 0/3] tty: xuartps: Fix build
Date: Tue, 29 Oct 2013 09:24:57 -0700 [thread overview]
Message-ID: <20131029162457.GA22189@kroah.com> (raw)
In-Reply-To: <1382398861-21542-1-git-send-email-soren.brinkmann@xilinx.com>
On Mon, Oct 21, 2013 at 04:40:58PM -0700, Soren Brinkmann wrote:
> This should fix the issues in the x86 build of the xuartps driver. The
> issues are:
> - [tty:tty-next 72/75] drivers/tty/serial/xilinx_uartps.c:436:7: error:
> 'PRE_RATE_CHANGE' undeclared
> - [tty:tty-next 73/75] drivers/tty/serial/xilinx_uartps.c:1227:21:
> error: 'xuartps_uart_driver' undeclared
>
> Additionally I found some build warnings while fixing those issues.
>
> There are some additional comments regarding patches 1 and 3 in their
> respective email.
> This series is based on the tty-next tree.
No it isn't, it doesn't apply there at all. Please respin these against
the latest tty-next branch and resend them so that I can apply them.
thanks,
greg k-h
next prev parent reply other threads:[~2013-10-29 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 23:40 [PATCH 0/3] tty: xuartps: Fix build Soren Brinkmann
2013-10-21 23:40 ` [PATCH 1/3] tty: xuartps: Fix "may be used uninitialized" build warning Soren Brinkmann
2013-10-29 16:22 ` Greg Kroah-Hartman
2013-10-29 16:39 ` Sören Brinkmann
2013-10-21 23:41 ` [PATCH 2/3] tty: xuartps: Fix build error due to missing forward declaration Soren Brinkmann
2013-10-21 23:41 ` [PATCH 3/3] tty: xuartps: Fix build error when COMMON_CLK is not set Soren Brinkmann
2013-10-29 16:24 ` Greg Kroah-Hartman [this message]
2013-10-29 16:26 ` [PATCH 0/3] tty: xuartps: Fix build Greg Kroah-Hartman
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=20131029162457.GA22189@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=soren.brinkmann@xilinx.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