All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] [PATCH v2] Remove sparse warnings in mdc_request.c
Date: Sat, 8 Apr 2017 13:02:37 +0200	[thread overview]
Message-ID: <20170408110237.GA6877@kroah.com> (raw)
In-Reply-To: <1491283537-13023-1-git-send-email-skanda.kashyap@gmail.com>

On Mon, Apr 03, 2017 at 10:25:37PM -0700, skanda.kashyap at gmail.com wrote:
> From: Skanda Guruanand <skanda.kashyap@gmail.com>
> 
> Signed-off-by: Skanda Guruanand <skanda.kashyap@gmail.com>

Changelog text goes between those two lines, right?

> 
> I have modified  struct lu_dirpage as suggested in lustre_idl.h file

Why the extra ' '?

> 
> CHECK   drivers/staging/lustre/lustre/mdc/mdc_request.c
> drivers/staging/lustre/lustre/mdc/mdc_request.c:958:42: warning: cast
> to restricted __le64

Why is this all wrapped?




> drivers/staging/lustre/lustre/mdc/mdc_request.c:959:42: warning: cast
> to restricted __le64
> drivers/staging/lustre/lustre/mdc/mdc_request.c:962:42: warning: cast
> to restricted __le64
> drivers/staging/lustre/lustre/mdc/mdc_request.c:963:42: warning: cast
> to restricted __le64
> drivers/staging/lustre/lustre/mdc/mdc_request.c:985:50: warning: cast
> to restricted __le32
> drivers/staging/lustre/lustre/mdc/mdc_request.c:1193:24: warning: cast
> to restricted __le64
> drivers/staging/lustre/lustre/mdc/mdc_request.c:1328:25: warning: cast
> to restricted __le64
> drivers/staging/lustre/lustre/mdc/mdc_request.c:1329:23: warning: cast
> to restricted __le64
> drivers/staging/lustre/lustre/mdc/mdc_request.c:1332:25: warning: cast
> to restricted __le64
> drivers/staging/lustre/lustre/mdc/mdc_request.c:1333:23: warning: cast
> to restricted __le64
> 
> ---
>  drivers/staging/lustre/lustre/include/lustre/lustre_idl.h | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/staging/lustre/lustre/include/lustre/lustre_idl.h b/drivers/staging/lustre/lustre/include/lustre/lustre_idl.h
> index 60b827e..df48b8d 100644
> --- a/drivers/staging/lustre/lustre/include/lustre/lustre_idl.h
> +++ b/drivers/staging/lustre/lustre/include/lustre/lustre_idl.h
> @@ -846,10 +846,10 @@ struct luda_type {
>  #endif
>  
>  struct lu_dirpage {
> -	__u64	    ldp_hash_start;
> -	__u64	    ldp_hash_end;
> -	__u32	    ldp_flags;
> -	__u32	    ldp_pad0;
> +	__le64	    ldp_hash_start;
> +	__le64	    ldp_hash_end;
> +	__le32	    ldp_flags;
> +	__le32	    ldp_pad0;


Are you sure this is correct?  How was it tested?

Also, please fix your subject to properly match those already made for
this driver...

thanks,

greg k-h

  parent reply	other threads:[~2017-04-08 11:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <58d9f73a.09c3620a.d471b.d171@mx.google.com>
2017-03-29  5:05 ` [lustre-devel] [PATCH] Remove sparse warnings in mdc_request.c Dilger, Andreas
     [not found]   ` <1490936959-6337-1-git-send-email-skanda.kashyap@gmail.com>
     [not found]     ` <1490936959-6337-2-git-send-email-skanda.kashyap@gmail.com>
2017-03-31  5:55       ` Greg KH
     [not found]   ` <1491283537-13023-1-git-send-email-skanda.kashyap@gmail.com>
2017-04-04  5:34     ` [lustre-devel] [PATCH v2] " Greg KH
2017-04-08 11:02     ` Greg KH [this message]
     [not found]       ` <1491887125-20397-1-git-send-email-skanda.kashyap@gmail.com>
2017-04-11  5:15         ` [lustre-devel] [PATCH v2] Fix endianness issues " Greg KH
     [not found]           ` <1491970957-26525-1-git-send-email-skanda.kashyap@gmail.com>
2017-04-12  6:15             ` Greg KH
     [not found]               ` <1492067363-31101-1-git-send-email-skanda.kashyap@gmail.com>
2017-04-14  8:15                 ` [lustre-devel] [PATCH v2] staging: lustre: Fix sparse endianness warnings cast to restricted __le64 and __le32 Greg KH
     [not found]                   ` <1492303739-32762-1-git-send-email-skanda.kashyap@gmail.com>
2017-04-18  9:54                     ` Dilger, Andreas

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=20170408110237.GA6877@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=lustre-devel@lists.lustre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.