All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiaofei Tan <tanxiaofei@huawei.com>
To: Jiri Slaby <jirislaby@kernel.org>, <gregkh@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>, <linuxarm@openeuler.org>
Subject: Re: [PATCH v2 04/10] tty: tty_jobctrl: Fix coding style issues of block comments
Date: Wed, 7 Apr 2021 14:57:53 +0800	[thread overview]
Message-ID: <8aca1b4a-df03-cb6a-3aa8-a071d2f1c0d3@huawei.com> (raw)
In-Reply-To: <87ba5be2-e8ee-b1ed-175d-1ee7d5a45498@kernel.org>

Hi Jiri,

On 2021/4/7 13:26, Jiri Slaby wrote:
> On 06. 04. 21, 13:24, Xiaofei Tan wrote:
>> Fix coding style issues of block comments, reported by checkpatch.pl.
>> Besides, do some expression optimization for the sentenses.
>>
>> Signed-off-by: Xiaofei Tan <tanxiaofei@huawei.com>
>> ---
>>   drivers/tty/tty_jobctrl.c | 16 ++++++++++------
>>   1 file changed, 10 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/tty/tty_jobctrl.c b/drivers/tty/tty_jobctrl.c
>> index 86070f7..7003b6b 100644
>> --- a/drivers/tty/tty_jobctrl.c
>> +++ b/drivers/tty/tty_jobctrl.c
>> @@ -204,8 +204,10 @@ int tty_signal_session_leader(struct tty_struct
>> *tty, int exit_session)
>>               spin_lock_irq(&p->sighand->siglock);
>>               if (p->signal->tty == tty) {
>>                   p->signal->tty = NULL;
>> -                /* We defer the dereferences outside fo
>> -                   the tasklist lock */
>> +                /*
>> +                 * We defer the dereferences outside of
>> +                 * the tasklist lock period
>
> :). No, I meant "period" as this punctuation mark: .
>

Oh, my misunderstanding. I will send v3 later. thanks. :)

>> +                 */
>>                   refs++;
>>               }
>>               if (!p->signal->leader) {
>> @@ -328,9 +330,11 @@ void disassociate_ctty(int on_exit)
>>    */
>>   void no_tty(void)
>>   {
>> -    /* FIXME: Review locking here. The tty_lock never covered any race
>> -       between a new association and proc_clear_tty but possible we need
>> -       to protect against this anyway */
>> +    /*
>> +     * FIXME: Review locking here. The tty_lock never covered any race
>> +     * between a new association and proc_clear_tty but possibly we need
>> +     * to protect against this period anyway
>
> The same here.
>

Sure

>> +     */
>>       struct task_struct *tsk = current;
>>         disassociate_ctty(0);
>> @@ -536,7 +540,7 @@ static int tiocgsid(struct tty_struct *tty, struct
>> tty_struct *real_tty, pid_t _
>>       /*
>>        * (tty == real_tty) is a cheap way of
>>        * testing if the tty is NOT a master pty.
>> -    */
>> +     */
>>       if (tty == real_tty && current->signal->tty != real_tty)
>>           return -ENOTTY;
>>
>
>


  reply	other threads:[~2021-04-07  6:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06 11:24 [PATCH v2 00/10] tty: Fix some coding style issues Xiaofei Tan
2021-04-06 11:24 ` [PATCH v2 01/10] tty/sysrq: Add a blank line after declarations Xiaofei Tan
2021-04-06 11:24 ` [PATCH v2 02/10] tty/sysrq: Fix issues of code indent should use tabs Xiaofei Tan
2021-04-06 11:24 ` [PATCH v2 03/10] tty: tty_jobctrl: Add a blank line after declarations Xiaofei Tan
2021-04-06 11:24 ` [PATCH v2 04/10] tty: tty_jobctrl: Fix coding style issues of block comments Xiaofei Tan
2021-04-07  5:26   ` Jiri Slaby
2021-04-07  6:57     ` Xiaofei Tan [this message]
2021-04-06 11:24 ` [PATCH v2 05/10] tty: tty_jobctrl: Remove spaces before tabs Xiaofei Tan
2021-04-06 11:24 ` [PATCH v2 06/10] tty: tty_ldisc: Fix an issue of code indent should use tabs Xiaofei Tan
2021-04-06 11:24 ` [PATCH v2 07/10] tty: tty_ldisc: Add a blank line after declarations Xiaofei Tan
2021-04-06 11:24 ` [PATCH v2 08/10] tty: tty_ldisc: Fix coding style issues of block comments Xiaofei Tan
2021-04-06 11:24 ` [PATCH v2 09/10] tty: tty_ldisc: Do not use assignment in if condition Xiaofei Tan
2021-04-06 11:24 ` [PATCH v2 10/10] tty: tty_ldisc: Remove the repeated word 'the' 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=8aca1b4a-df03-cb6a-3aa8-a071d2f1c0d3@huawei.com \
    --to=tanxiaofei@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@openeuler.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 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.