Re: [PATCH v1 1/1] process: export symbols for fork/exit tracing functions

[Greg Kroah-Hartman]

On Mon, Jun 12, 2023 at 11:15:41PM +0800, jim.tsai wrote:
> Export the tracing function "sched_process_fork" and
> "sched_process_exit" for process statistics.
> 
> Change-Id: I67dcdcb26371cd7a495ff0b210361742b1a2088e
> Signed-off-by: jim.tsai <Wei-chin.Tsai@xxxxxxxxxxxx>

You might want to run scripts/checkpatch.pl on your patch before you
send it out again, you don't need a change-id line.

Also, here's what my bot says:

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 contains warnings and/or errors noticed by the
  scripts/checkpatch.pl tool.

- You did not specify a description of why the patch is needed, or
  possibly, any description at all, in the email body.  Please read the
  section entitled "The canonical patch format" in the kernel file,
  Documentation/process/submitting-patches.rst for what is needed in
  order to properly describe the change.

- You did not write a descriptive Subject: for the patch, allowing Greg,
  and everyone else, to know what this patch is all about.  Please read
  the section entitled "The canonical patch format" in the kernel file,
  Documentation/process/submitting-patches.rst for what a proper
  Subject: line should look like.

- It looks like you did not use your "real" name for the patch on either
  the Signed-off-by: line, or the From: line (both of which have to
  match).  Please read the kernel file,
  Documentation/process/submitting-patches.rst for how to do this
  correctly.

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