[PATCH] Fix line over 80 characters

[PATCH] Fix line over 80 characters

[Gokce Kuler]

Signed-off-by: Gokce Kuler <gokcekuler@gmail.com>
---
 drivers/staging/exfat/exfat_core.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/staging/exfat/exfat_core.c b/drivers/staging/exfat/exfat_core.c
index b23fbf3..e4777e8 100644
--- a/drivers/staging/exfat/exfat_core.c
+++ b/drivers/staging/exfat/exfat_core.c
@@ -2312,7 +2312,8 @@ s32 exfat_find_dir_entry(struct super_block *sb, struct chain_t *p_dir,
 
 				if ((entry_type == TYPE_FILE) || (entry_type == TYPE_DIR)) {
 					file_ep = (struct file_dentry_t *)ep;
-					if ((type == TYPE_ALL) || (type == entry_type)) {
+					if ((type == TYPE_ALL) ||
+			         	    (type == entry_type)) {
 						num_ext_entries = file_ep->num_ext;
 						is_feasible_entry = true;
 					} else {
-- 
2.7.4

Re: [PATCH] Fix line over 80 characters

[Greg KH]

On Tue, Dec 17, 2019 at 11:03:17PM +0300, Gokce Kuler wrote:
> Signed-off-by: Gokce Kuler <gokcekuler@gmail.com>
> ---
>  drivers/staging/exfat/exfat_core.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/exfat/exfat_core.c b/drivers/staging/exfat/exfat_core.c
> index b23fbf3..e4777e8 100644
> --- a/drivers/staging/exfat/exfat_core.c
> +++ b/drivers/staging/exfat/exfat_core.c
> @@ -2312,7 +2312,8 @@ s32 exfat_find_dir_entry(struct super_block *sb, struct chain_t *p_dir,
>  
>  				if ((entry_type == TYPE_FILE) || (entry_type == TYPE_DIR)) {
>  					file_ep = (struct file_dentry_t *)ep;
> -					if ((type == TYPE_ALL) || (type == entry_type)) {
> +					if ((type == TYPE_ALL) ||
> +			         	    (type == entry_type)) {
>  						num_ext_entries = file_ep->num_ext;
>  						is_feasible_entry = true;
>  					} else {
> -- 
> 2.7.4
>


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 was sent privately to Greg.  Kernel development is done in
  public, please always cc: a public mailing list with a patch
  submission.  Using the tool, scripts/get_maintainer.pl on the patch
  will tell you what mailing list to cc.

- 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.

- 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

[PATCH] Fix line over 80 characters

[Gokce Kuler]

Fix line over 80 characters
Signed-off-by: Gokce Kuler <gokcekuler@gmail.com>
---
 drivers/staging/exfat/exfat_super.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/staging/exfat/exfat_super.c b/drivers/staging/exfat/exfat_super.c
index 1ae5a77..37e424f 100644
--- a/drivers/staging/exfat/exfat_super.c
+++ b/drivers/staging/exfat/exfat_super.c
@@ -2161,7 +2161,8 @@ static int ffsRemoveDir(struct inode *inode, struct file_id_t *fid)
 	mutex_lock(&p_fs->v_mutex);
 
 	clu_to_free.dir = fid->start_clu;
-	clu_to_free.size = (s32)((fid->size - 1) >> p_fs->cluster_size_bits) + 1;
+	clu_to_free.size = (s32)((fid->size - 1) >>
+		       	p_fs->cluster_size_bits) + 1;
 	clu_to_free.flags = fid->flags;
 
 	if (!is_dir_empty(sb, &clu_to_free)) {
-- 
2.7.4

Re: [PATCH] Fix line over 80 characters

[Greg KH]

On Sat, Mar 07, 2020 at 11:24:09PM +0300, Gokce Kuler wrote:
> Fix line over 80 characters
> Signed-off-by: Gokce Kuler <gokcekuler@gmail.com>
> ---
>  drivers/staging/exfat/exfat_super.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/exfat/exfat_super.c b/drivers/staging/exfat/exfat_super.c
> index 1ae5a77..37e424f 100644
> --- a/drivers/staging/exfat/exfat_super.c
> +++ b/drivers/staging/exfat/exfat_super.c
> @@ -2161,7 +2161,8 @@ static int ffsRemoveDir(struct inode *inode, struct file_id_t *fid)
>  	mutex_lock(&p_fs->v_mutex);
>  
>  	clu_to_free.dir = fid->start_clu;
> -	clu_to_free.size = (s32)((fid->size - 1) >> p_fs->cluster_size_bits) + 1;
> +	clu_to_free.size = (s32)((fid->size - 1) >>
> +		       	p_fs->cluster_size_bits) + 1;
>  	clu_to_free.flags = fid->flags;
>  
>  	if (!is_dir_empty(sb, &clu_to_free)) {
> -- 
> 2.7.4
> 

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