linux-kernel - Re: [PATCH] staging: comedi: clean up debugging code in #if 0 or 1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <X+L7fjlFKWHEwwJh@kroah.com>
Date:   Wed, 23 Dec 2020 09:10:38 +0100
From:   Greg KH <greg@...ah.com>
To:     chensong <chensong_2000@....cn>
Cc:     linux-kernel@...r.kernel.org, abbotti@....co.uk,
        hsweeten@...ionengravers.com, chensong@...kylinos.cn
Subject: Re: [PATCH] staging: comedi: clean up debugging code in #if 0 or 1

On Wed, Dec 23, 2020 at 10:20:44AM +0800, chensong wrote:
> There are a log of "#if 0" or "#if 1" in comedi driver which
> cause warning when running checkpatch.pl, they are supposed to
> be cleaned up before release.
> 
> Signed-off-by: chensong <chensong_2000@....cn>

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:

- 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/SubmittingPatches
  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