From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: James Simmons <jsimmons@infradead.org>
Cc: <devel@driverdev.osuosl.org>,
Andreas Dilger <andreas.dilger@intel.com>,
Oleg Drokin <oleg.drokin@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lustre Development List <lustre-devel@lists.lustre.org>
Subject: Re: [PATCH v2 0/6] staging: lustre: update modinfo data
Date: Fri, 26 Feb 2016 06:03:45 +0000 [thread overview]
Message-ID: <20160226060343.GA29216@kroah.com> (raw)
In-Reply-To: <1456448832-959-1-git-send-email-jsimmons@infradead.org>
On Thu, Feb 25, 2016 at 08:07:06PM -0500, James Simmons wrote:
> The module information for Lustre is stale or in some cases
> completely missing. This collection of patches brings the
> modinfo up to date as well as filling in any missing information.
> This patch set has been redone to rebase it on Oleg's latest
> patch set to avoid collisons in merging.
>
> Andreas Dilger (4):
> staging: lustre: add missing MODULE_AUTHOR for LNet selftest module
> staging: lustre: update the MODULE_DESCRIPTION for all lustre modules
> staging: lustre: make module_init/exit naming consistent
> staging: lustre: update comment for lnet_lib_init/exit
>
> James Simmons (2):
> staging: lustre: move module info to end of libcfs module.c file
> staging: lustre: update the MODULE_VERSION for all lustre modules
What changed to need a v2 of this series?
Please ALWAYS say what the difference is, don't expect us to "just
know".
Please send a v3 of this, describing the changes, in the correct format,
in each patch. You know better than this...
thanks,
greg k-h
next prev parent reply other threads:[~2016-02-26 6:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 1:07 [PATCH v2 0/6] staging: lustre: update modinfo data James Simmons
2016-02-26 1:07 ` [PATCH v2 1/6] staging: lustre: move module info to end of libcfs module.c file James Simmons
2016-02-26 1:07 ` [PATCH v2 2/6] staging: lustre: add missing MODULE_AUTHOR for LNet selftest module James Simmons
2016-02-26 1:07 ` [PATCH v2 3/6] staging: lustre: update the MODULE_VERSION for all lustre modules James Simmons
2016-02-26 1:07 ` [PATCH v2 4/6] staging: lustre: update the MODULE_DESCRIPTION " James Simmons
2016-02-26 1:07 ` [PATCH v2 5/6] staging: lustre: make module_init/exit naming consistent James Simmons
2016-02-26 1:07 ` [PATCH v2 6/6] staging: lustre: update comment for lnet_lib_init/exit James Simmons
2016-02-26 6:03 ` Greg Kroah-Hartman [this message]
2016-02-26 6:11 ` [lustre-devel] [PATCH v2 0/6] staging: lustre: update modinfo data Drokin, Oleg
2016-02-26 6:25 ` Greg Kroah-Hartman
2016-02-26 15:46 ` Simmons, James A.
2016-02-26 16:18 ` 'Greg Kroah-Hartman'
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=20160226060343.GA29216@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=jsimmons@infradead.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