linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel.org>
To: "Sathish Kumar Balasubramaniam -ERS,
	HCL Tech"  <b-sathishkumar@hcl.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>
Subject: Re: [PATCH] tty: serial: UART driver for RISC-V based Chromite SoC family
Date: Sat, 28 Aug 2021 09:55:00 +0200	[thread overview]
Message-ID: <c5ef817e-7ae9-ae93-a3c4-08fecb943c53@kernel.org> (raw)
In-Reply-To: <SG2PR04MB3820B2DED21B7B5DB868A18F81C89@SG2PR04MB3820.apcprd04.prod.outlook.com>

On 27. 08. 21, 18:32, Sathish Kumar Balasubramaniam -ERS, HCL Tech wrote:
> +static void chromite_serial_set_termios(struct uart_port *port,
> +                                               struct ktermios *termios,
> +                                               struct ktermios *old) {
> +       struct chromite_serial_port *csp = port_to_chromite_serial_port(port);
> +       unsigned long flags;
> +       int rate;
> +
> +       if ((termios->c_cflag & CSIZE) != CS8)
> +               dev_err_once(csp->port.dev, "only 8-bit words supported\n");
> +       if (termios->c_cflag & CSTOPB)
> +               dev_err_once(csp->port.dev, "only 1 stop-bit is supported\n");
> +       if (termios->c_iflag & (INPCK | PARMRK))
> +               dev_err_once(csp->port.dev, "parity checking not supported\n");
> +       if (termios->c_iflag & BRKINT)
> +               dev_err_once(csp->port.dev, "BREAK detection not
> + supported\n");

Many mangled lines like this. Please fix these up in v2. And also use 
checkpatch. The function-opening { above should be on a separate line 
(on many locations).

thanks,
-- 
js

  parent reply	other threads:[~2021-08-28  7:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-27 16:23 [PATCH] tty: serial: UART driver for RISC-V based Chromite SoC family Sathish Kumar Balasubramaniam -ERS, HCL Tech
2021-08-27 16:30 ` Greg Kroah-Hartman
2021-08-27 16:32 ` Sathish Kumar Balasubramaniam -ERS, HCL Tech
2021-08-27 17:26   ` Greg Kroah-Hartman
2021-08-28 16:54     ` Sathish Kumar Balasubramaniam -ERS, HCL Tech
2021-08-28  7:55   ` Jiri Slaby [this message]
2021-08-28 16:59     ` Sathish Kumar Balasubramaniam -ERS, HCL Tech
2021-08-28 17:16       ` Sathish Kumar Balasubramaniam -ERS, HCL Tech
2021-08-29  7:09         ` Jiri Slaby

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=c5ef817e-7ae9-ae93-a3c4-08fecb943c53@kernel.org \
    --to=jirislaby@kernel.org \
    --cc=b-sathishkumar@hcl.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-serial@vger.kernel.org \
    /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).