From: James Simmons <jsimmons@infradead.org>
To: Joe Perches <joe@perches.com>
Cc: "Drokin, Oleg" <oleg.drokin@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"<devel@driverdev.osuosl.org>" <devel@driverdev.osuosl.org>,
"<linux-kernel@vger.kernel.org>" <linux-kernel@vger.kernel.org>,
"<lustre-devel@lists.lustre.org>" <lustre-devel@lists.lustre.org>
Subject: Re: [lustre-devel] [RFC PATCH 0/3] staging: lustre: detypede
Date: Fri, 1 Apr 2016 21:03:07 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.20.1604012102020.17701@casper.infradead.org> (raw)
In-Reply-To: <alpine.LFD.2.20.1604012045090.17701@casper.infradead.org>
Sorry I was seeing a email error that I thought was preventing my email
being sent out. That is not the case.
next prev parent reply other threads:[~2016-04-01 20:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 13:02 [RFC PATCH 0/3] staging: lustre: detypedef Joe Perches
2016-04-01 13:02 ` [RFC PATCH 1/3] staging: lustre: Remove typedef lnet_peer_t Joe Perches
2016-04-01 13:02 ` [RFC PATCH 2/3] staging: lustre: Remove typedef lnd_t Joe Perches
2016-04-01 13:02 ` [RFC PATCH 3/3] staging: lustre: Remove typedef lnet_msg_t Joe Perches
2016-04-01 14:23 ` [lustre-devel] [RFC PATCH 0/3] staging: lustre: detypedef Drokin, Oleg
2016-04-01 18:44 ` Joe Perches
2016-04-01 19:14 ` Drokin, Oleg
2016-04-01 19:27 ` Joe Perches
2016-04-01 19:56 ` James Simmons
2016-04-01 20:03 ` James Simmons [this message]
2016-04-01 19:56 ` James Simmons
2016-04-01 19:57 ` James Simmons
2016-04-01 19:57 ` James Simmons
2016-04-01 19:59 ` James Simmons
2016-04-01 15:58 ` Simmons, James A.
2016-04-01 18:54 ` Joe Perches
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=alpine.LFD.2.20.1604012102020.17701@casper.infradead.org \
--to=jsimmons@infradead.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--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®