All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jay Fang <f.fangjian@huawei.com>
To: <gregkh@linuxfoundation.org>
Cc: <linux-serial@vger.kernel.org>, <linuxarm@huawei.com>,
	<huangdaode@huawei.com>, <tangzihao1@hisilicon.com>
Subject: [PATCH 00/11] tty: serial: Fix some coding style issues
Date: Tue, 18 May 2021 09:57:07 +0800	[thread overview]
Message-ID: <1621303038-12062-1-git-send-email-f.fangjian@huawei.com> (raw)

From: Zihao Tang <tangzihao1@hisilicon.com>

This patchset fixes some coding style issues reported by checkpatch.pl.

Zihao Tang (11):
  tty: serial: 21285: Fix some coding sytle issues
  tty: serial: amba-pl010: Fix 2 coding style issues
  tty: serial: amba-pl011: Replace the unsuitable spaces with tabs
  tty: serial: amba-pl011: Remove initialization of static variable
  tty: serial: apbuart: Fix some coding sytle issues
  tty: serial: atmel: Fix some coding style issues
  tty: serial: bcm63xx_uart: Fix some coding style issues
  tty: serial: clps711x: Fix some coding style issuses
  tty: serial: digicolor: Use 'unsigned int' instead of 'unsigned'
  tty: serial: dz: Use 'unsigned int' instead of 'unsigned'
  tty: serial: earlycon-arm-semihost : Fix some coding style issuses

 drivers/tty/serial/21285.c                 |  7 +++----
 drivers/tty/serial/amba-pl010.c            |  4 ++--
 drivers/tty/serial/amba-pl011.c            | 12 ++++++------
 drivers/tty/serial/apbuart.c               |  5 ++++-
 drivers/tty/serial/atmel_serial.c          | 13 +++++++++----
 drivers/tty/serial/bcm63xx_uart.c          | 14 +++++++++-----
 drivers/tty/serial/clps711x.c              |  4 ++--
 drivers/tty/serial/digicolor-usart.c       |  2 +-
 drivers/tty/serial/dz.c                    |  4 ++--
 drivers/tty/serial/earlycon-arm-semihost.c |  3 ++-
 10 files changed, 40 insertions(+), 28 deletions(-)

-- 
2.7.4


             reply	other threads:[~2021-05-18  1:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18  1:57 Jay Fang [this message]
2021-05-18  1:57 ` [PATCH 01/11] tty: serial: 21285: Fix some coding sytle issues Jay Fang
2021-05-18  1:57 ` [PATCH 02/11] tty: serial: amba-pl010: Fix 2 coding style issues Jay Fang
2021-05-18  1:57 ` [PATCH 03/11] tty: serial: amba-pl011: Replace the unsuitable spaces with tabs Jay Fang
2021-05-18  1:57 ` [PATCH 04/11] tty: serial: amba-pl011: Remove initialization of static variable Jay Fang
2021-05-18  1:57 ` [PATCH 05/11] tty: serial: apbuart: Fix some coding sytle issues Jay Fang
2021-05-18  1:57 ` [PATCH 06/11] tty: serial: atmel: Fix some coding style issues Jay Fang
2021-05-18  1:57 ` [PATCH 07/11] tty: serial: bcm63xx_uart: " Jay Fang
2021-05-18  1:57 ` [PATCH 08/11] tty: serial: clps711x: Fix some coding style issuses Jay Fang
2021-05-18  1:57 ` [PATCH 09/11] tty: serial: digicolor: Use 'unsigned int' instead of 'unsigned' Jay Fang
2021-05-18  1:57 ` [PATCH 10/11] tty: serial: dz: " Jay Fang
2021-05-18  1:57 ` [PATCH 11/11] tty: serial: earlycon-arm-semihost : Fix some coding style issuses Jay Fang
2021-05-18  5:39 ` [PATCH 00/11] tty: serial: Fix some coding style issues Greg KH
2021-05-21  8:56 ` Johan Hovold

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=1621303038-12062-1-git-send-email-f.fangjian@huawei.com \
    --to=f.fangjian@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=huangdaode@huawei.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=tangzihao1@hisilicon.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 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.