Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp153192pxf; Tue, 6 Apr 2021 17:54:56 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw75x1FoII19YwfaqDHjR5aZDUnBNnM8iXNChqVodO//UiKE5NtUgETP5ewEQKCO07nmYmP X-Received: by 2002:a5e:9503:: with SMTP id r3mr466173ioj.142.1617756896549; Tue, 06 Apr 2021 17:54:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617756896; cv=none; d=google.com; s=arc-20160816; b=rB7oA2XOpG+gbqIImiDIP/tb8sf2bID4xt0YOjSte4VUBqTLbQutzXGNTiVSD6v16H /ekr46TK7I3vj3nllxpPjRFae4ShgjlfrdE+WWxhwSyCe5ytZ/dQnlI00ugWNuHnATJf 0vosLp4+gBqvj39IlI++VMUNwEKq1/aDKmFUHzDAx8VE9C5ANfQeG4Cc4m3WAXjbuJJo dsXapzvKzuwsl8sggn3mDWP9HBkbj0QATiwzSImo/engqojZm2sbAkYaHd4hR6Ho1vf7 9wnISV7AhN4iwSYmTFk/kenMmzJyTGaT7lGNIzgyuHeUvhWHhGta24E7psWZWL3AzJol KZkA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:in-reply-to:message-id :date:subject:cc:to:from; bh=5iEtDRoPrvYbe4TODzTEKXCxGpU1sq0HdvXn8SATqV8=; b=tj7Ref8pV9f5JniEz31NCi1EgQzkAphj4WJRbMpJGRO0C4iZCpjLcv6jXBw+WJC0dC G0hToLMLwPjpMYqUFivKEqY1SfjtJrgmRXjuRejq7hDdbq3k4jWOAyGZLc9rn0pcqhqS 5TRFcKOG2s2n9ENkYsWUVruwRir8YJhBSeqklK9Uf8ztcDvb1vfN3jYYdDHyMFzeXqCX TbQCtxxcQn9QlfnKkvbhugHdCSxMJzS7dwC2hwS6+9w3oA6ESGainrUHXuErvbPJ3Dw5 sZ946jrBr0b3///zuFJpt4oLxPAUa9HmyhqFNcc7QrFYBRRKIQsB/iraEkFQawd213v3 bL9w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id x17si20605852ile.87.2021.04.06.17.54.42; Tue, 06 Apr 2021 17:54:56 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S245572AbhDFL2B (ORCPT + 99 others); Tue, 6 Apr 2021 07:28:01 -0400 Received: from szxga07-in.huawei.com ([45.249.212.35]:16355 "EHLO szxga07-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S245511AbhDFL1o (ORCPT ); Tue, 6 Apr 2021 07:27:44 -0400 Received: from DGGEMS409-HUB.china.huawei.com (unknown [172.30.72.60]) by szxga07-in.huawei.com (SkyGuard) with ESMTP id 4FF4vP6x4rz9405; Tue, 6 Apr 2021 19:25:21 +0800 (CST) Received: from localhost.localdomain (10.67.165.24) by DGGEMS409-HUB.china.huawei.com (10.3.19.209) with Microsoft SMTP Server id 14.3.498.0; Tue, 6 Apr 2021 19:27:25 +0800 From: Xiaofei Tan To: , CC: , , Xiaofei Tan Subject: [PATCH v2 08/10] tty: tty_ldisc: Fix coding style issues of block comments Date: Tue, 6 Apr 2021 19:24:46 +0800 Message-ID: <1617708288-14847-9-git-send-email-tanxiaofei@huawei.com> X-Mailer: git-send-email 2.8.1 In-Reply-To: <1617708288-14847-1-git-send-email-tanxiaofei@huawei.com> References: <1617708288-14847-1-git-send-email-tanxiaofei@huawei.com> MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.67.165.24] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Fix coding style issues of block comments, reported by checkpatch.pl. Signed-off-by: Xiaofei Tan --- drivers/tty/tty_ldisc.c | 32 ++++++++++++++++++++------------ 1 file changed, 20 insertions(+), 12 deletions(-) diff --git a/drivers/tty/tty_ldisc.c b/drivers/tty/tty_ldisc.c index df0b589..874d238 100644 --- a/drivers/tty/tty_ldisc.c +++ b/drivers/tty/tty_ldisc.c @@ -529,9 +529,11 @@ static void tty_ldisc_restore(struct tty_struct *tty, struct tty_ldisc *old) const char *name = tty_name(tty); pr_warn("Falling back ldisc for %s.\n", name); - /* The traditional behaviour is to fall back to N_TTY, we - want to avoid falling back to N_NULL unless we have no - choice to avoid the risk of breaking anything */ + /* + * The traditional behaviour is to fall back to N_TTY, we + * want to avoid falling back to N_NULL unless we have no + * choice to avoid the risk of breaking anything + */ if (tty_ldisc_failto(tty, N_TTY) < 0 && tty_ldisc_failto(tty, N_NULL) < 0) panic("Couldn't open N_NULL ldisc for %s.", name); @@ -600,17 +602,21 @@ int tty_set_ldisc(struct tty_struct *tty, int disc) up_read(&tty->termios_rwsem); } - /* At this point we hold a reference to the new ldisc and a - reference to the old ldisc, or we hold two references to - the old ldisc (if it was restored as part of error cleanup - above). In either case, releasing a single reference from - the old ldisc is correct. */ + /* + * At this point we hold a reference to the new ldisc and a + * reference to the old ldisc, or we hold two references to + * the old ldisc (if it was restored as part of error cleanup + * above). In either case, releasing a single reference from + * the old ldisc is correct. + */ new_ldisc = old_ldisc; out: tty_ldisc_unlock(tty); - /* Restart the work queue in case no characters kick it off. Safe if - already running */ + /* + * Restart the work queue in case no characters kick it off. Safe if + * already running + */ tty_buffer_restart_work(tty->port); err: tty_ldisc_put(new_ldisc); /* drop the extra reference */ @@ -812,8 +818,10 @@ void tty_ldisc_release(struct tty_struct *tty) tty_ldisc_kill(o_tty); tty_ldisc_unlock_pair(tty, o_tty); - /* And the memory resources remaining (buffers, termios) will be - disposed of when the kref hits zero */ + /* + * And the memory resources remaining (buffers, termios) will be + * disposed of when the kref hits zero + */ tty_ldisc_debug(tty, "released\n"); } -- 2.8.1