From: "Dilger, Andreas" <andreas.dilger@intel.com>
To: "Guillermo O. Freschi" <kedrot@gmail.com>
Cc: "Drokin, Oleg" <oleg.drokin@intel.com>,
"lustre-devel@lists.lustre.org" <lustre-devel@lists.lustre.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [lustre-devel] [PATCH 1/2] Fixed signedness check
Date: Fri, 13 Jan 2017 01:17:39 +0000 [thread overview]
Message-ID: <0EF6ABF1-1E3F-46DF-90CA-DA890027DEC4@intel.com> (raw)
In-Reply-To: <20161226154339.8916-1-kedrot@gmail.com>
On Dec 26, 2016, at 08:43, Guillermo O. Freschi <kedrot@gmail.com> wrote:
>
> Was `unsigned int`, but `enum`s are signed.
Interesting that GCC didn't complain that the itree_overlap_cb() function
signature didn't match the argument prototype for interval_search():
typedef enum interval_iter (*interval_callback_t)(struct interval_node *node,
void *args);
In the end it is a somewhat cosmetic fix, because the only enum values
(1, 2) were unsigned, but good to be consistent. Thanks for the fix.
> Signed-off-by: Guillermo O. Freschi <kedrot@gmail.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
> ---
> drivers/staging/lustre/lustre/ldlm/ldlm_lock.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/lustre/lustre/ldlm/ldlm_lock.c b/drivers/staging/lustre/lustre/ldlm/ldlm_lock.c
> index a4a291acb659..f4cbc89b4f24 100644
> --- a/drivers/staging/lustre/lustre/ldlm/ldlm_lock.c
> +++ b/drivers/staging/lustre/lustre/ldlm/ldlm_lock.c
> @@ -1148,7 +1148,7 @@ static int lock_matches(struct ldlm_lock *lock, struct lock_match_data *data)
> return INTERVAL_ITER_STOP;
> }
>
> -static unsigned int itree_overlap_cb(struct interval_node *in, void *args)
> +static enum interval_iter itree_overlap_cb(struct interval_node *in, void *args)
> {
> struct ldlm_interval *node = to_ldlm_interval(in);
> struct lock_match_data *data = args;
> --
> 2.11.0
>
> _______________________________________________
> lustre-devel mailing list
> lustre-devel@lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
prev parent reply other threads:[~2017-01-13 1:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-26 15:43 Guillermo O. Freschi
2016-12-26 15:43 ` [PATCH 2/2] Style fixes Guillermo O. Freschi
2017-01-13 1:20 ` [lustre-devel] " Dilger, Andreas
2017-01-13 20:48 ` [PATCH v2] " Guillermo O. Freschi
2017-01-16 16:45 ` Oleg Drokin
2017-01-13 1:17 ` Dilger, Andreas [this message]
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=0EF6ABF1-1E3F-46DF-90CA-DA890027DEC4@intel.com \
--to=andreas.dilger@intel.com \
--cc=kedrot@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®