From: Xiaofei Tan <tanxiaofei@huawei.com> To: <gregkh@linuxfoundation.org>, <jirislaby@kernel.org> Cc: <linux-kernel@vger.kernel.org>, <linuxppc-dev@lists.ozlabs.org>, <linuxarm@openeuler.org>, Xiaofei Tan <tanxiaofei@huawei.com> Subject: [PATCH 2/9] tty: hvc_console: Fix "foo * bar" should be "foo *bar" Date: Mon, 17 May 2021 14:37:06 +0800 [thread overview] Message-ID: <1621233433-27094-3-git-send-email-tanxiaofei@huawei.com> (raw) In-Reply-To: <1621233433-27094-1-git-send-email-tanxiaofei@huawei.com> Fix "foo * bar" should be "foo *bar", reported by checkpatch.pl. Signed-off-by: Xiaofei Tan <tanxiaofei@huawei.com> --- drivers/tty/hvc/hvc_console.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/tty/hvc/hvc_console.c b/drivers/tty/hvc/hvc_console.c index a1eca9d..ddf07ff 100644 --- a/drivers/tty/hvc/hvc_console.c +++ b/drivers/tty/hvc/hvc_console.c @@ -344,7 +344,7 @@ static int hvc_install(struct tty_driver *driver, struct tty_struct *tty) * The TTY interface won't be used until after the vio layer has exposed the vty * adapter to the kernel. */ -static int hvc_open(struct tty_struct *tty, struct file * filp) +static int hvc_open(struct tty_struct *tty, struct file *filp) { struct hvc_struct *hp = tty->driver_data; unsigned long flags; @@ -386,7 +386,7 @@ static int hvc_open(struct tty_struct *tty, struct file * filp) return rc; } -static void hvc_close(struct tty_struct *tty, struct file * filp) +static void hvc_close(struct tty_struct *tty, struct file *filp) { struct hvc_struct *hp = tty->driver_data; unsigned long flags; -- 2.8.1
WARNING: multiple messages have this Message-ID (diff)
From: Xiaofei Tan <tanxiaofei@huawei.com> To: <gregkh@linuxfoundation.org>, <jirislaby@kernel.org> Cc: Xiaofei Tan <tanxiaofei@huawei.com>, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, linuxarm@openeuler.org Subject: [PATCH 2/9] tty: hvc_console: Fix "foo * bar" should be "foo *bar" Date: Mon, 17 May 2021 14:37:06 +0800 [thread overview] Message-ID: <1621233433-27094-3-git-send-email-tanxiaofei@huawei.com> (raw) In-Reply-To: <1621233433-27094-1-git-send-email-tanxiaofei@huawei.com> Fix "foo * bar" should be "foo *bar", reported by checkpatch.pl. Signed-off-by: Xiaofei Tan <tanxiaofei@huawei.com> --- drivers/tty/hvc/hvc_console.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/tty/hvc/hvc_console.c b/drivers/tty/hvc/hvc_console.c index a1eca9d..ddf07ff 100644 --- a/drivers/tty/hvc/hvc_console.c +++ b/drivers/tty/hvc/hvc_console.c @@ -344,7 +344,7 @@ static int hvc_install(struct tty_driver *driver, struct tty_struct *tty) * The TTY interface won't be used until after the vio layer has exposed the vty * adapter to the kernel. */ -static int hvc_open(struct tty_struct *tty, struct file * filp) +static int hvc_open(struct tty_struct *tty, struct file *filp) { struct hvc_struct *hp = tty->driver_data; unsigned long flags; @@ -386,7 +386,7 @@ static int hvc_open(struct tty_struct *tty, struct file * filp) return rc; } -static void hvc_close(struct tty_struct *tty, struct file * filp) +static void hvc_close(struct tty_struct *tty, struct file *filp) { struct hvc_struct *hp = tty->driver_data; unsigned long flags; -- 2.8.1
next prev parent reply other threads:[~2021-05-17 6:41 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-17 6:37 [PATCH 0/9] tty: hvc_console: Fix some coding style issues Xiaofei Tan 2021-05-17 6:37 ` Xiaofei Tan 2021-05-17 6:37 ` [PATCH 1/9] tty: hvc_console: Fix spaces required around that '=' Xiaofei Tan 2021-05-17 6:37 ` Xiaofei Tan 2021-05-17 6:37 ` Xiaofei Tan [this message] 2021-05-17 6:37 ` [PATCH 2/9] tty: hvc_console: Fix "foo * bar" should be "foo *bar" Xiaofei Tan 2021-05-17 6:37 ` [PATCH 3/9] tty: hvc_console: Remove trailing whitespace Xiaofei Tan 2021-05-17 6:37 ` Xiaofei Tan 2021-05-17 6:37 ` [PATCH 4/9] tty: hvc_console: Fix issues of code indent should use tabs Xiaofei Tan 2021-05-17 6:37 ` Xiaofei Tan 2021-05-17 6:37 ` [PATCH 5/9] tty: hvc_console: Delete spaces prohibited around open parenthesis '(' and ')' Xiaofei Tan 2021-05-17 6:37 ` Xiaofei Tan 2021-05-17 6:37 ` [PATCH 6/9] tty: hvc_console: Fix coding style issues of block comments Xiaofei Tan 2021-05-17 6:37 ` Xiaofei Tan 2021-05-17 14:15 ` Johan Hovold 2021-05-17 14:15 ` Johan Hovold 2021-05-18 4:01 ` Xiaofei Tan 2021-05-18 4:01 ` Xiaofei Tan 2021-05-20 8:21 ` Johan Hovold 2021-05-20 8:21 ` Johan Hovold 2021-05-20 13:21 ` Xiaofei Tan 2021-05-20 13:21 ` Xiaofei Tan 2021-05-20 13:52 ` Johan Hovold 2021-05-20 13:52 ` Johan Hovold 2021-05-21 2:23 ` Xiaofei Tan 2021-05-21 2:23 ` Xiaofei Tan 2021-05-20 15:21 ` Joe Perches 2021-05-20 15:21 ` Joe Perches 2021-05-21 8:44 ` Johan Hovold 2021-05-21 8:44 ` Johan Hovold 2021-05-17 6:37 ` [PATCH 7/9] tty: hvc_console: Add a blank line after declarations Xiaofei Tan 2021-05-17 6:37 ` Xiaofei Tan 2021-05-17 6:37 ` [PATCH 8/9] tty: hvc_console: Remove the repeated words 'no' and 'from' Xiaofei Tan 2021-05-17 6:37 ` Xiaofei Tan 2021-05-17 6:37 ` [PATCH 9/9] tty: hvc_console: Move open brace { on the previous line Xiaofei Tan 2021-05-17 6:37 ` Xiaofei Tan 2021-05-20 15:11 ` [PATCH 0/9] tty: hvc_console: Fix some coding style issues Greg KH 2021-05-20 15:11 ` Greg KH 2021-05-21 2:18 ` Xiaofei Tan 2021-05-21 2:18 ` Xiaofei Tan
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=1621233433-27094-3-git-send-email-tanxiaofei@huawei.com \ --to=tanxiaofei@huawei.com \ --cc=gregkh@linuxfoundation.org \ --cc=jirislaby@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linuxarm@openeuler.org \ --cc=linuxppc-dev@lists.ozlabs.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: linkBe 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.