public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Earl Chew <earl.chew@yahoo.ca>
Cc: linux-kernel@vger.kernel.org, jirislaby@kernel.org,
	peter@hurleysoftware.com
Subject: Re: [PATCH v2 0/3] tty: Fix tiocspgrp() related races
Date: Thu, 28 Sep 2023 15:38:54 +0200	[thread overview]
Message-ID: <2023092838-banking-sturdily-8e28@gregkh> (raw)
In-Reply-To: <20230928130658.4045344-1-earl.chew@yahoo.ca>

On Thu, Sep 28, 2023 at 06:06:56AM -0700, Earl Chew wrote:
> This is a resubmission to correct errors and warnings
> called out by the kernel test robot.
> 
> Earl Chew (3):
>   tty: Fix __tty_check_change() and tiocspgrp() race
>   tty: Serialise racing tiocspgrp() callers
>   tty: Move task_pgrp() after tty->ctrl.lock for consistency
> 
>  drivers/tty/tty_jobctrl.c | 47 ++++++++++++++++++++++++++++-----------
>  1 file changed, 34 insertions(+), 13 deletions(-)
> 
> -- 
> 2.39.1

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
a patch that has triggered this response.  He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created.  Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- This looks like a new version of a previously submitted patch, but you
  did not list below the --- line any changes from the previous version.
  Please read the section entitled "The canonical patch format" in the
  kernel file, Documentation/process/submitting-patches.rst for what
  needs to be done here to properly describe this.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot

  reply	other threads:[~2023-09-28 13:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230831143645.2298799-1-earl_chew@yahoo.com>
2023-09-01  1:50 ` [PATCH 0/3] tty: Fix tiocspgrp() related races Earl Chew
2023-09-28 13:06   ` [PATCH v2 " Earl Chew
2023-09-28 13:38     ` Greg KH [this message]
2023-09-28 13:06   ` [PATCH v2 1/3] tty: Fix __tty_check_change() and tiocspgrp() race Earl Chew
2023-09-28 13:06   ` [PATCH v2 2/3] tty: Serialise racing tiocspgrp() callers Earl Chew
2023-09-29  6:07     ` kernel test robot
2023-09-28 13:06   ` [PATCH v2 3/3] tty: Move task_pgrp() after tty->ctrl.lock for consistency Earl Chew
2023-09-01  1:50 ` [PATCH 1/3] tty: Fix __tty_check_change() and tiocspgrp() race Earl Chew
2023-09-01  1:50 ` [PATCH 2/3] tty: Serialise racing tiocspgrp() callers Earl Chew
2023-09-01 16:09   ` kernel test robot
2023-09-01 17:14   ` kernel test robot
2023-09-28 21:00   ` kernel test robot
2023-09-01  1:50 ` [PATCH 3/3] tty: Move task_pgrp() after tty->ctrl.lock for consistency Earl Chew

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=2023092838-banking-sturdily-8e28@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=earl.chew@yahoo.ca \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@hurleysoftware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox