From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Dilger, Andreas" <andreas.dilger@intel.com>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
James Simmons <jsimmons@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Drokin, Oleg" <oleg.drokin@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"lustre-devel@lists.lustre.org" <lustre-devel@lists.lustre.org>
Subject: Re: [PATCH v2] staging: lustre: remove IOC_LIBCFS_PING_TEST ioctl
Date: Mon, 21 Dec 2015 14:06:15 -0800 [thread overview]
Message-ID: <20151221220615.GB14211@kroah.com> (raw)
In-Reply-To: <D27D2340.11CC89%andreas.dilger@intel.com>
On Fri, Nov 27, 2015 at 04:31:39AM +0000, Dilger, Andreas wrote:
> On 2015/11/08, 09:34, "James Simmons" <jsimmons@infradead.org> wrote:
>
> >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:
>
> Hi Greg,
> are you planning on pushing this patch to Linus for 4.4? It was resent
> on 11/08 per your request on 11/07 but I don't see it in staging or
> staging-next yet. Since it fixes the depmod dependency cycle for
> allmodconfig builds on mainline it seems worthwhile to include into
> 4.4-rc3 rather than waiting for 4.5.
No one told me it fixed a bug, let me see if it's still even needed...
next prev parent reply other threads:[~2015-12-21 22:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 4:31 [lustre-devel] [PATCH v2] staging: lustre: remove IOC_LIBCFS_PING_TEST ioctl Dilger, Andreas
2015-11-27 4:31 ` Dilger, Andreas
2015-12-21 22:06 ` Greg Kroah-Hartman [this message]
2015-12-21 22:18 ` Linus Torvalds
2015-12-21 22:21 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2015-11-08 16:34 James Simmons
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=20151221220615.GB14211@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=torvalds@linux-foundation.org \
/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.