From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: y@ccs.ornl.gov
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, James Simmons <uja.ornl@yahoo.com>,
James Simmons <jsimmons@infradead.org>
Subject: Re: [PATCH] staging: lustre: remove IOC_LIBCFS_PING_TEST ioctl
Date: Fri, 6 Nov 2015 19:27:47 -0800 [thread overview]
Message-ID: <20151107032747.GA14108@kroah.com> (raw)
In-Reply-To: <563d5d08.0347370a.f9d83.2af9SMTPIN_ADDED_BROKEN@mx.google.com>
On Fri, Nov 06, 2015 at 09:08:03PM -0500, y@ccs.ornl.gov wrote:
> From: James Simmons <uja.ornl@yahoo.com>
>
> The ioctl IOC_LIBCFS_PING_TEST has not been used in
> ages. The recent nidstring changes which moved all
> the nidstring operations from libcfs to the LNet
> layer but this ioctl code was still using an
> nidstring operation that was causing an circular
> dependency loop between libcfs and LNet.
>
> Signed-off-by: James Simmons <jsimmons@infradead.org>
> ---
> .../lustre/include/linux/libcfs/libcfs_ioctl.h | 1 -
> drivers/staging/lustre/lustre/libcfs/module.c | 17 -----------------
> 2 files changed, 0 insertions(+), 18 deletions(-)
You sent me 2 copies of this, which am I supposed to apply? I've
dropped both, please resend the correct one.
thanks,
greg k-h
next parent reply other threads:[~2015-11-07 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <563d5d08.0347370a.f9d83.2af9SMTPIN_ADDED_BROKEN@mx.google.com>
2015-11-07 3:27 ` Greg Kroah-Hartman [this message]
2015-11-07 2:08 [PATCH] staging: lustre: remove IOC_LIBCFS_PING_TEST ioctl y
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=20151107032747.GA14108@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 \
--cc=uja.ornl@yahoo.com \
--cc=y@ccs.ornl.gov \
/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;
as well as URLs for NNTP newsgroup(s).