From: Tobin C. Harding <me@tobin.cc>
To: Stefano Manni <stefano.manni@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>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
lustre-devel@lists.lustre.org
Subject: [lustre-devel] [PATCH 0/4] staging: lustre: fixed some signedness warns from sparse
Date: Thu, 23 Nov 2017 15:59:26 +1100 [thread overview]
Message-ID: <20171123045926.GD12736@eros> (raw)
In-Reply-To: <20171122193831.11801-1-stefano.manni@gmail.com>
On Wed, Nov 22, 2017 at 08:38:27PM +0100, Stefano Manni wrote:
> Fixed some signedness warnings from sparse on lustre.
>
> Stefano Manni (4):
> staging: lustre: fixed signedness of some socklnd params
> staging: lustre: fixed signedness of llite
> staging: lustre: fixed signedness of lov
> staging: lustre: fixed signedness of obdclass
You may like to use imperative mood for your git log brief descriptions
Stefano.
s/fixed/fix/
For justification see Documentation/process/submitting-patches.rst.
Specifically section 2 of that document.
Hope this helps,
Tobin.
> drivers/staging/lustre/lnet/klnds/socklnd/socklnd.h | 4 ++--
> .../staging/lustre/lnet/klnds/socklnd/socklnd_modparams.c | 2 +-
> drivers/staging/lustre/lustre/llite/dir.c | 3 ++-
> drivers/staging/lustre/lustre/llite/llite_lib.c | 9 ++++++---
> drivers/staging/lustre/lustre/llite/lproc_llite.c | 14 ++++++--------
> drivers/staging/lustre/lustre/lov/lov_obd.c | 2 +-
> drivers/staging/lustre/lustre/lov/lov_offset.c | 11 +++++++----
> drivers/staging/lustre/lustre/obdclass/obd_mount.c | 2 +-
> 8 files changed, 26 insertions(+), 21 deletions(-)
>
> --
> 2.5.5
>
> _______________________________________________
> devel mailing list
> devel at linuxdriverproject.org
> http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Tobin C. Harding" <me@tobin.cc>
To: Stefano Manni <stefano.manni@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>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
lustre-devel@lists.lustre.org
Subject: Re: [PATCH 0/4] staging: lustre: fixed some signedness warns from sparse
Date: Thu, 23 Nov 2017 15:59:26 +1100 [thread overview]
Message-ID: <20171123045926.GD12736@eros> (raw)
In-Reply-To: <20171122193831.11801-1-stefano.manni@gmail.com>
On Wed, Nov 22, 2017 at 08:38:27PM +0100, Stefano Manni wrote:
> Fixed some signedness warnings from sparse on lustre.
>
> Stefano Manni (4):
> staging: lustre: fixed signedness of some socklnd params
> staging: lustre: fixed signedness of llite
> staging: lustre: fixed signedness of lov
> staging: lustre: fixed signedness of obdclass
You may like to use imperative mood for your git log brief descriptions
Stefano.
s/fixed/fix/
For justification see Documentation/process/submitting-patches.rst.
Specifically section 2 of that document.
Hope this helps,
Tobin.
> drivers/staging/lustre/lnet/klnds/socklnd/socklnd.h | 4 ++--
> .../staging/lustre/lnet/klnds/socklnd/socklnd_modparams.c | 2 +-
> drivers/staging/lustre/lustre/llite/dir.c | 3 ++-
> drivers/staging/lustre/lustre/llite/llite_lib.c | 9 ++++++---
> drivers/staging/lustre/lustre/llite/lproc_llite.c | 14 ++++++--------
> drivers/staging/lustre/lustre/lov/lov_obd.c | 2 +-
> drivers/staging/lustre/lustre/lov/lov_offset.c | 11 +++++++----
> drivers/staging/lustre/lustre/obdclass/obd_mount.c | 2 +-
> 8 files changed, 26 insertions(+), 21 deletions(-)
>
> --
> 2.5.5
>
> _______________________________________________
> devel mailing list
> devel@linuxdriverproject.org
> http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2017-11-23 4:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 19:38 [PATCH 0/4] staging: lustre: fixed some signedness warns from sparse Stefano Manni
2017-11-22 19:38 ` [PATCH 1/4] staging: lustre: fixed signedness of some socklnd params Stefano Manni
2017-11-23 12:13 ` [lustre-devel] " Dan Carpenter
2017-11-23 12:13 ` Dan Carpenter
2017-11-23 23:47 ` Stefano Manni
2017-11-24 12:49 ` [lustre-devel] " Dan Carpenter
2017-11-24 12:49 ` Dan Carpenter
2017-11-22 19:38 ` [PATCH 2/4] staging: lustre: fixed signedness of llite Stefano Manni
2017-11-22 19:38 ` [PATCH 3/4] staging: lustre: fixed signedness of lov Stefano Manni
2017-11-24 15:42 ` [lustre-devel] " Greg Kroah-Hartman
2017-11-24 15:42 ` Greg Kroah-Hartman
2017-11-22 19:38 ` [PATCH 4/4] staging: lustre: fixed signedness of obdclass Stefano Manni
2017-11-23 4:59 ` Tobin C. Harding [this message]
2017-11-23 4:59 ` [PATCH 0/4] staging: lustre: fixed some signedness warns from sparse Tobin C. Harding
2017-11-23 11:51 ` [lustre-devel] " Dan Carpenter
2017-11-23 11:51 ` Dan Carpenter
2017-11-23 22:20 ` [lustre-devel] " Tobin C. Harding
2017-11-23 22:20 ` Tobin C. Harding
2017-11-23 23:32 ` Stefano Manni
2017-11-24 13:02 ` [lustre-devel] " Dan Carpenter
2017-11-24 13:02 ` Dan Carpenter
2017-11-24 21:37 ` [lustre-devel] " Tobin C. Harding
2017-11-24 21:37 ` Tobin C. Harding
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=20171123045926.GD12736@eros \
--to=me@tobin.cc \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=oleg.drokin@intel.com \
--cc=stefano.manni@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.