[PATCH 2/2] NETLOGIC: Kconfig: Fixed help and coding style warnings

[PATCH 2/2] NETLOGIC: Kconfig: Fixed help and coding style warnings

[Tamir Suliman]

Fixed Coding style issues

Signed-off-by: Tamir Suliman <tsuliman@linuxvaults.com>
---
 drivers/staging/netlogic/Kconfig | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/drivers/staging/netlogic/Kconfig b/drivers/staging/netlogic/Kconfig
index d660de5..6e8e56a 100644
--- a/drivers/staging/netlogic/Kconfig
+++ b/drivers/staging/netlogic/Kconfig
@@ -2,6 +2,8 @@ config NETLOGIC_XLR_NET
 	tristate "Netlogic XLR/XLS network device"
 	depends on CPU_XLR
 	select PHYLIB
-	---help---
+	help
 	This driver support Netlogic XLR/XLS on chip gigabit
-	Ethernet.
+	Ethernet.The XLR/XLS NAE blocks can be configured as one 10G
+	interface or four 1G interfaces. This driver supports blocks
+	with 1G ports.
-- 
1.8.3.1

Re: [PATCH 2/2] NETLOGIC: Kconfig: Fixed help and coding style warnings

[Greg KH]

On Sat, Jun 30, 2018 at 02:30:44PM +0000, Tamir Suliman wrote:
> Fixed Coding style issues
> 
> Signed-off-by: Tamir Suliman <tsuliman@linuxvaults.com>
> ---
>  drivers/staging/netlogic/Kconfig | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/staging/netlogic/Kconfig b/drivers/staging/netlogic/Kconfig
> index d660de5..6e8e56a 100644
> --- a/drivers/staging/netlogic/Kconfig
> +++ b/drivers/staging/netlogic/Kconfig
> @@ -2,6 +2,8 @@ config NETLOGIC_XLR_NET
>  	tristate "Netlogic XLR/XLS network device"
>  	depends on CPU_XLR
>  	select PHYLIB
> -	---help---
> +	help
>  	This driver support Netlogic XLR/XLS on chip gigabit
> -	Ethernet.
> +	Ethernet.The XLR/XLS NAE blocks can be configured as one 10G
> +	interface or four 1G interfaces. This driver supports blocks
> +	with 1G ports.
> -- 
> 1.8.3.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:

- 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/SubmittingPatches 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/SubmittingPatches for what a proper Subject: line should
  look like.

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