mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "René Nyffenegger" <mail@renenyffenegger.ch>
Cc: cristian.ciocaltea@gmail.com, masahiroy@kernel.org,
	cmllamas@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Update comment (addition of gtags) in cripts/tags.sh
Date: Sun, 17 Dec 2023 09:26:55 +0100	[thread overview]
Message-ID: <2023121742-handed-upper-88a0@gregkh> (raw)
In-Reply-To: <20231216211232.2699-1-mail@renenyffenegger.ch>

On Sat, Dec 16, 2023 at 10:12:32PM +0100, René Nyffenegger wrote:
> Commit f4ed1009fcea (kbuild: add GNU GLOBAL tags generation) added support
> for the GNU Global source tagging system. However, this addition
> was not reflected in the script's header comment.
> 
> Fixes: f4ed1009fcea ("kbuild: add GNU GLOBAL tags generation")
> Signed-off-by: René Nyffenegger <mail@renenyffenegger.ch>
> ---
>  scripts/tags.sh | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/scripts/tags.sh b/scripts/tags.sh
> index a70d43723..cb9696134 100755
> --- a/scripts/tags.sh
> +++ b/scripts/tags.sh
> @@ -3,7 +3,7 @@
>  # Generate tags or cscope files
>  # Usage tags.sh <mode>
>  #
> -# mode may be any of: tags, TAGS, cscope
> +# mode may be any of: tags, gtags, TAGS, cscope
>  #
>  # Uses the following environment variables:
>  # SUBARCH, SRCARCH, srctree
> -- 
> 2.30.2
> 

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-12-17  8:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-16 21:12 René Nyffenegger
2023-12-17  8:26 ` Greg KH [this message]

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=2023121742-handed-upper-88a0@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cmllamas@google.com \
    --cc=cristian.ciocaltea@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@renenyffenegger.ch \
    --cc=masahiroy@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®