From: Greg KH <gregkh@linuxfoundation.org>
To: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
Cc: oleg.drokin@intel.com, andreas.dilger@intel.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
lustre-devel@lists.lustre.org
Subject: Re: [PATCH v2 0/6] Patch series to make lustre safe(r) for W=1 compiles
Date: Mon, 21 Dec 2015 15:43:54 -0800 [thread overview]
Message-ID: <20151221234354.GB8211@kroah.com> (raw)
In-Reply-To: <1449875065-35182-1-git-send-email-Valdis.Kletnieks@vt.edu>
On Fri, Dec 11, 2015 at 06:04:19PM -0500, Valdis Kletnieks wrote:
> Start of a batch series to clean up the Lustre tree. Other people have
> done some sparse and checkpatch cleanups, but I found a bunch of
> stuff building with W=1. There's probably more, but this was the
> really low-hanging obvious fruit.
>
> Valdis Kletnieks (6):
> staging/lustre: Silence warning about 'inline'
> staging/lustre: Fix set-but-unused whinge.
> staging/lustre: Clean up another C warnining: set but not used
> staging/lustre: Fix another C compiler whine: set but not used
> staging/lustre: Nuke an unsigned >= 0 assert
> staging/lustre: Nuke another unsigned >= 0 assert
These subject names don't match what you actually sent out, the 'prefix'
got stripped. Please resend them all so that I can properly apply them.
thanks,
greg k-h
prev parent reply other threads:[~2015-12-21 23:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 23:04 Valdis Kletnieks
2015-12-11 23:04 ` [PATCH v2 1/6] staging/lustre: Silence warning about 'inline' Valdis Kletnieks
2015-12-11 23:04 ` [PATCH v2 2/6] Fix set-but-unused whinge Valdis Kletnieks
2015-12-11 23:04 ` [PATCH v2 3/6] Clean up another C warnining: set but not used Valdis Kletnieks
2015-12-11 23:04 ` [PATCH v2 4/6] Fix another C compiler whine: " Valdis Kletnieks
2015-12-11 23:04 ` [PATCH v2 5/6] Nuke an unsigned >= 0 assert Valdis Kletnieks
2015-12-11 23:04 ` [PATCH v2 6/6] Nuke another " Valdis Kletnieks
2015-12-21 23:43 ` Greg KH [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=20151221234354.GB8211@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--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®