mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: KuoHsiang Chou <kuohsiang_chou@aspeedtech.com>,
	tzimmermann@suse.de, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, airlied@redhat.com, airlied@linux.ie,
	daniel@ffwll.ch, jenmin_yuan@aspeedtech.com,
	kuohsiang_chou@aspeedtech.com, arc_sung@aspeedtech.com,
	tommy_huang@aspeedtech.com
Subject: [PATCH] drm/ast: fix semicolon.cocci warnings
Date: Sun, 2 Jan 2022 03:41:32 +0800	[thread overview]
Message-ID: <20220101194131.GA11806@0607766062a2> (raw)
In-Reply-To: <20211122103617.3496-1-kuohsiang_chou@aspeedtech.com>

From: kernel test robot <lkp@intel.com>

drivers/gpu/drm/ast/ast_dp.c:166:3-4: Unneeded semicolon


 Remove unneeded semicolon.

Generated by: scripts/coccinelle/misc/semicolon.cocci

CC: KuoHsiang Chou <kuohsiang_chou@aspeedtech.com>
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---

url:    https://github.com/0day-ci/linux/commits/KuoHsiang-Chou/drm-ast-Create-the-driver-for-ASPEED-proprietory-Display-Port/20211122-183830
base:   git://anongit.freedesktop.org/drm/drm drm-next
:::::: branch date: 6 weeks ago
:::::: commit date: 6 weeks ago

 ast_dp.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/drivers/gpu/drm/ast/ast_dp.c
+++ b/drivers/gpu/drm/ast/ast_dp.c
@@ -163,7 +163,7 @@ bool ast_dp_launch(struct drm_device *de
 				bDPExecute = 0;
 				break;
 			}
-		};
+		}
 
 		if (bDPExecute)
 			ast->tx_chip_type = AST_TX_ASTDP;

  parent reply	other threads:[~2022-01-01 19:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 10:36 [PATCH] drm/ast: Create the driver for ASPEED proprietory Display-Port KuoHsiang Chou
2021-11-25 15:49 ` [PATCH] drm/ast: fix semicolon.cocci warnings kernel test robot
2021-11-25 15:56 ` [PATCH] drm/ast: Create the driver for ASPEED proprietory Display-Port kernel test robot
2021-12-03  6:31 ` Kuo-Hsiang Chou
2021-12-03  8:54   ` Thomas Zimmermann
2021-12-27  8:37     ` [PATCH v2] " KuoHsiang Chou
2022-01-01 19:41 ` kernel test robot [this message]
2022-01-01 19:51 ` [PATCH] " kernel test robot
2022-01-04  8:50   ` [PATCH v3] " KuoHsiang Chou
2022-01-12 15:04     ` Thomas Zimmermann
2022-04-28  7:56       ` [PATCH v4] " KuoHsiang Chou
2022-05-04  7:27         ` Thomas Zimmermann
     [not found]           ` <PSAPR06MB48056FC903142B7F60A3BD388CC39@PSAPR06MB4805.apcprd06.prod.outlook.com>
2022-05-04  9:37             ` Thomas Zimmermann
2022-05-05  2:41               ` Kuo-Hsiang Chou
2022-05-05  2:51                 ` Luke Chen
2022-05-10 10:56             ` Thomas Zimmermann
2022-05-13  9:07               ` Kuo-Hsiang Chou
2022-05-13 10:20                 ` Thomas Zimmermann
2022-05-13 10:39                   ` Kuo-Hsiang Chou
2022-05-30  6:05                     ` Kuo-Hsiang Chou
2022-06-01 10:42                       ` Thomas Zimmermann

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=20220101194131.GA11806@0607766062a2 \
    --to=lkp@intel.com \
    --cc=airlied@linux.ie \
    --cc=airlied@redhat.com \
    --cc=arc_sung@aspeedtech.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jenmin_yuan@aspeedtech.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kuohsiang_chou@aspeedtech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tommy_huang@aspeedtech.com \
    --cc=tzimmermann@suse.de \
    /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

Powered by JetHome