From: Greg KH <gregkh@linuxfoundation.org>
To: Shalin Mehta <shalinmehta85@gmail.com>
Cc: oleg.drokin@intel.com, andreas.dilger@intel.com,
kernel-janitors@lists.osdl.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, lustre-devel@lists.lustre.org
Subject: [lustre-devel] [PATCH] staging: lustre: Fixed the parenthesis
Date: Mon, 15 Feb 2016 18:28:12 -0800 [thread overview]
Message-ID: <20160216022812.GA25122@kroah.com> (raw)
In-Reply-To: <1455507422-13568-1-git-send-email-shalinmehta85@gmail.com>
On Sun, Feb 14, 2016 at 07:37:02PM -0800, Shalin Mehta wrote:
> The parentehsis are fixed in the macro for the ldlm lock to set and
> clear the flags.
"fixed" in what way? Did you test-build this patch? Also, you
mispelled a word here...
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Shalin Mehta <shalinmehta85@gmail.com>
Cc: oleg.drokin@intel.com, andreas.dilger@intel.com,
kernel-janitors@lists.osdl.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, lustre-devel@lists.lustre.org
Subject: Re: [PATCH] staging: lustre: Fixed the parenthesis
Date: Mon, 15 Feb 2016 18:28:12 -0800 [thread overview]
Message-ID: <20160216022812.GA25122@kroah.com> (raw)
In-Reply-To: <1455507422-13568-1-git-send-email-shalinmehta85@gmail.com>
On Sun, Feb 14, 2016 at 07:37:02PM -0800, Shalin Mehta wrote:
> The parentehsis are fixed in the macro for the ldlm lock to set and
> clear the flags.
"fixed" in what way? Did you test-build this patch? Also, you
mispelled a word here...
thanks,
greg k-h
next prev parent reply other threads:[~2016-02-16 2:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 3:37 [lustre-devel] [PATCH] staging: lustre: Fixed the parenthesis Shalin Mehta
2016-02-15 3:37 ` Shalin Mehta
2016-02-16 2:28 ` Greg KH [this message]
2016-02-16 2:28 ` Greg KH
2016-02-16 2:41 ` [lustre-devel] " Drokin, Oleg
2016-02-16 2:41 ` Drokin, Oleg
2016-02-16 2:51 ` [lustre-devel] " Drokin, Oleg
2016-02-16 2:51 ` Drokin, Oleg
2016-02-17 6:39 ` shalin mehta
2016-02-17 6:39 ` shalin mehta
2016-02-19 10:22 ` Dan Carpenter
2016-02-19 10:22 ` Dan Carpenter
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=20160216022812.GA25122@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=kernel-janitors@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=oleg.drokin@intel.com \
--cc=shalinmehta85@gmail.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.