From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: James Simmons <jsimmons@infradead.org>
Cc: devel@driverdev.osuosl.org, Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
lustre-devel@lists.lustre.org
Subject: Re: [PATCH 00/13] bring lustre's kernel_comm code up to date
Date: Mon, 21 Dec 2015 15:37:37 -0800 [thread overview]
Message-ID: <20151221233737.GA11987@kroah.com> (raw)
In-Reply-To: <1447010238-25775-1-git-send-email-jsimmons@infradead.org>
On Sun, Nov 08, 2015 at 02:17:05PM -0500, James Simmons wrote:
> This patch series brings the kernel_comm code used by Lustre up
> to the latest verison with various fixes and style improvements
> which makes the code compliant with the linux kernel standard.
This series does not apply, please rebase against my staging-testing
branch and resend.
thanks,
greg k-h
prev parent reply other threads:[~2015-12-21 23:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 19:17 [lustre-devel] [PATCH 00/13] bring lustre's kernel_comm code up to date James Simmons
2015-11-08 19:17 ` James Simmons
2015-11-08 19:17 ` [lustre-devel] [PATCH 01/13] staging: lustre: remove hsm_nl proc file James Simmons
2015-11-08 19:17 ` James Simmons
2015-11-08 19:17 ` [lustre-devel] [PATCH 02/13] staging: lustre: kg_sem semaphore handling is incorrectly James Simmons
2015-11-08 19:17 ` James Simmons
2015-11-08 19:17 ` [lustre-devel] [PATCH 03/13] staging: lustre: Prevent duplicate CT registrations James Simmons
2015-11-08 19:17 ` James Simmons
2015-11-08 19:17 ` [lustre-devel] [PATCH 04/13] staging: lustre: move kernel_user_comm.c from libcfs to lustre James Simmons
2015-11-08 19:17 ` James Simmons
2015-11-08 19:17 ` [lustre-devel] [PATCH 05/13] staging: lustre: split kernel comm between user and kernel James Simmons
2015-11-08 19:17 ` James Simmons
2015-11-08 19:17 ` [lustre-devel] [PATCH 06/13] staging: lustre: embed kr_data into kkuc_reg James Simmons
2015-11-08 19:17 ` James Simmons
2015-11-08 19:17 ` [lustre-devel] [PATCH 07/13] staging: lustre: convert kernelcomm group to unsigned int James Simmons
2015-11-08 19:17 ` James Simmons
2015-11-08 19:17 ` [lustre-devel] [PATCH 08/13] staging: lustre: remove unnecessary NULL checks in kernel_comm.c James Simmons
2015-11-08 19:17 ` James Simmons
2015-11-08 19:17 ` [lustre-devel] [PATCH 09/13] staging: lustre: cleanup block comment style in kernel_comm code James Simmons
2015-11-08 19:17 ` James Simmons
2015-11-08 19:17 ` [lustre-devel] [PATCH 10/13] staging: lustre: add space around '+' " James Simmons
2015-11-08 19:17 ` James Simmons
2015-11-08 19:17 ` [lustre-devel] [PATCH 11/13] staging: lustre: use proper braces in libcfs_kkuc_group_put James Simmons
2015-11-08 19:17 ` James Simmons
2015-11-08 19:17 ` [lustre-devel] [PATCH 12/13] staging: lustre: return proper error code for libcfs_kkuc_msg_put James Simmons
2015-11-08 19:17 ` James Simmons
2015-11-08 19:17 ` [lustre-devel] [PATCH 13/13] staging: lustre: cleanup white space in kernel comm code James Simmons
2015-11-08 19:17 ` James Simmons
2015-12-21 23:37 ` Greg Kroah-Hartman [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=20151221233737.GA11987@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 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.