From: Dan Carpenter <dan.carpenter@oracle.com>
To: Quentin Lambert <lambert.quentin@gmail.com>
Cc: Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>,
James Simmons <jsimmons@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
lustre-devel@lists.lustre.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] staging: lustre: Fix variable type declaration after refactoring
Date: Thu, 08 Dec 2016 19:36:21 +0000 [thread overview]
Message-ID: <20161208193620.GX8176@mwanda> (raw)
In-Reply-To: <20161208160759.19649-1-lambert.quentin@gmail.com>
On Thu, Dec 08, 2016 at 05:07:59PM +0100, Quentin Lambert wrote:
> A recent clean-up declared och_flags as a int rather than fmode_t. This
> lead to the following sparse warning:
>
> drivers/staging/lustre/lustre/llite/file.c:106:30: warning: restricted
> fmode_t degrades to integer
>
> This patch fixes this issue.
>
> Fixes: 1200991234f7 ("staging: lustre: cleanup lustre_lib.h")
0a1200991234f7
Fixes hash is wrong. It should start with "0a".
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Quentin Lambert <lambert.quentin@gmail.com>
Cc: Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>,
James Simmons <jsimmons@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
lustre-devel@lists.lustre.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: [lustre-devel] [PATCH] staging: lustre: Fix variable type declaration after refactoring
Date: Thu, 8 Dec 2016 22:36:21 +0300 [thread overview]
Message-ID: <20161208193620.GX8176@mwanda> (raw)
In-Reply-To: <20161208160759.19649-1-lambert.quentin@gmail.com>
On Thu, Dec 08, 2016 at 05:07:59PM +0100, Quentin Lambert wrote:
> A recent clean-up declared och_flags as a int rather than fmode_t. This
> lead to the following sparse warning:
>
> drivers/staging/lustre/lustre/llite/file.c:106:30: warning: restricted
> fmode_t degrades to integer
>
> This patch fixes this issue.
>
> Fixes: 1200991234f7 ("staging: lustre: cleanup lustre_lib.h")
0a1200991234f7
Fixes hash is wrong. It should start with "0a".
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Quentin Lambert <lambert.quentin@gmail.com>
Cc: Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>,
James Simmons <jsimmons@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
lustre-devel@lists.lustre.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] staging: lustre: Fix variable type declaration after refactoring
Date: Thu, 8 Dec 2016 22:36:21 +0300 [thread overview]
Message-ID: <20161208193620.GX8176@mwanda> (raw)
In-Reply-To: <20161208160759.19649-1-lambert.quentin@gmail.com>
On Thu, Dec 08, 2016 at 05:07:59PM +0100, Quentin Lambert wrote:
> A recent clean-up declared och_flags as a int rather than fmode_t. This
> lead to the following sparse warning:
>
> drivers/staging/lustre/lustre/llite/file.c:106:30: warning: restricted
> fmode_t degrades to integer
>
> This patch fixes this issue.
>
> Fixes: 1200991234f7 ("staging: lustre: cleanup lustre_lib.h")
0a1200991234f7
Fixes hash is wrong. It should start with "0a".
regards,
dan carpenter
next prev parent reply other threads:[~2016-12-08 19:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 16:07 [PATCH] staging: lustre: Fix variable type declaration after refactoring Quentin Lambert
2016-12-08 16:07 ` Quentin Lambert
2016-12-08 16:07 ` [lustre-devel] " Quentin Lambert
2016-12-08 19:36 ` Dan Carpenter [this message]
2016-12-08 19:36 ` Dan Carpenter
2016-12-08 19:36 ` [lustre-devel] " Dan Carpenter
2016-12-08 20:38 ` [PATCH v2] " Quentin Lambert
2016-12-08 20:38 ` Quentin Lambert
2016-12-08 20:38 ` [lustre-devel] " Quentin Lambert
2016-12-19 16:38 ` James Simmons
2016-12-19 16:38 ` James Simmons
2016-12-19 16:38 ` [lustre-devel] " James Simmons
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=20161208193620.GX8176@mwanda \
--to=dan.carpenter@oracle.com \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jsimmons@infradead.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=lambert.quentin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=oleg.drokin@intel.com \
/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.