linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: Paul Walmsley <paul@pwsan.com>,
	Wesley Terpstra <wesley@sifive.com>,
	Palmer Dabbelt <palmer@sifive.com>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	Jiri Slaby <jslaby@suse.com>,
	linux-riscv@lists.infradead.org
Subject: Re: [PATCH 2/2] tty: serial: add driver for the SiFive UART
Date: Fri, 9 Nov 2018 08:59:51 -0800	[thread overview]
Message-ID: <20181109165951.GA13927@kroah.com> (raw)
Message-ID: <20181109165951.Pmdf49yWnO6GVBNbAyKzu1FtjnIvR1GhlUXT6fGeE48@z> (raw)
In-Reply-To: <20181018234352.26788-3-paul.walmsley@sifive.com>

On Thu, Oct 18, 2018 at 04:43:54PM -0700, Paul Walmsley wrote:
> Add a serial driver for the SiFive UART, found on SiFive FU540 devices
> (among others).
> 
> The underlying serial IP block is relatively basic, and currently does
> not support serial break detection.  Further information on the IP
> block can be found in the documentation and Chisel sources:
> 
> https://static.dev.sifive.com/FU540-C000-v1.0.pdf
> 
> https://github.com/sifive/sifive-blocks/tree/master/src/main/scala/devices/uart
> 
> This driver was written in collaboration with Wesley Terpstra
> <wesley@sifive.com>.
> 
> Boot-tested on a SiFive HiFive Unleashed A00 board.
> 
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Jiri Slaby <jslaby@suse.com>
> Cc: Palmer Dabbelt <palmer@sifive.com>
> Cc: Wesley Terpstra <wesley@sifive.com>
> Cc: linux-serial@vger.kernel.org
> Cc: linux-riscv@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Paul Walmsley <paul.walmsley@sifive.com>
> Signed-off-by: Paul Walmsley <paul@pwsan.com>
> ---
>  drivers/tty/serial/Kconfig       |   24 +
>  drivers/tty/serial/Makefile      |    1 +
>  drivers/tty/serial/sifive.c      | 1070 ++++++++++++++++++++++++++++++
>  include/uapi/linux/serial_core.h |    3 +
>  4 files changed, 1098 insertions(+)
>  create mode 100644 drivers/tty/serial/sifive.c

Seems like the 0-day bot did not like this driver, can you fix up those
build errors and resend?

thanks,

greg k-h

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2018-11-09 17:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181018234352.26788-1-paul.walmsley@sifive.com>
2018-10-18 23:43 ` [PATCH 1/2] dt-bindings: serial: add documentation for the SiFive UART driver Paul Walmsley
2018-10-18 23:43   ` Paul Walmsley
2018-10-19 16:51   ` Palmer Dabbelt
2018-10-19 16:51     ` Palmer Dabbelt
2018-10-18 23:43 ` [PATCH 2/2] tty: serial: add driver for the SiFive UART Paul Walmsley
2018-10-18 23:43   ` Paul Walmsley
2018-10-19  9:55   ` kbuild test robot
2018-10-19  9:55     ` kbuild test robot
2018-10-19 10:40   ` kbuild test robot
2018-10-19 10:40     ` kbuild test robot
2018-11-09 16:59   ` Greg Kroah-Hartman [this message]
2018-11-09 16:59     ` Greg Kroah-Hartman
2018-11-09 17:00     ` Greg Kroah-Hartman
2018-11-09 17:00       ` 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=20181109165951.GA13927@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=palmer@sifive.com \
    --cc=paul.walmsley@sifive.com \
    --cc=paul@pwsan.com \
    --cc=wesley@sifive.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;
as well as URLs for NNTP newsgroup(s).