Date:   Thu, 16 Mar 2023 07:44:39 +0100
From:   Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To:     Hanno =?iso-8859-1?Q?B=F6ck?= <hanno@hboeck.de>
Cc:     Jiri Slaby <jirislaby@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH]Fix typo in LEGACY_TIOCSTI Kconfig description
Message-ID: <ZBK614GE0HDTSVDE@kroah.com>
References: <20230315201400.7bb07d47.hanno@hboeck.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20230315201400.7bb07d47.hanno@hboeck.de>
Precedence: bulk

On Wed, Mar 15, 2023 at 08:14:00PM +0100, Hanno B?ck wrote:
> There is a stray ' in the description before the Y. It appears this was
> meant as a quote for the 'Y'. However, it is more common to use
> unquoted Y in Kconfig descriptions.
> 
> diff --git a/drivers/tty/Kconfig b/drivers/tty/Kconfig
> index d35fc068d..84caac32f 100644
> --- a/drivers/tty/Kconfig
> +++ b/drivers/tty/Kconfig
> @@ -160,7 +160,7 @@ config LEGACY_TIOCSTI
>  	  a dangerous legacy operation, and can be disabled on most
>  	  systems.
>  
> -	  Say 'Y here only if you have confirmed that your system's
> +	  Say Y here only if you have confirmed that your system's
>  	  userspace depends on this functionality to continue operating
>  	  normally.
>  

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:

- Your patch does not have a Signed-off-by: line.  Please read the
  kernel file, Documentation/process/submitting-patches.rst and resend
  it after adding that line.  Note, the line needs to be in the body of
  the email, before the patch, not at the bottom of the patch or in the
  email signature.

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