From: Andreas Dilger <adilger@dilger.ca>
To: Christoph Hellwig <hch@infradead.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>,
James Simmons <jsimmons@infradead.org>,
lustre-devel <lustre-devel@lists.lustre.org>,
fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
selinux@tycho.nsa.gov
Subject: Re: [PATCH] staging: lustre: delete the filesystem from the tree.
Date: Fri, 1 Jun 2018 14:20:27 -0400 [thread overview]
Message-ID: <E5BF8501-35EB-4DDF-ADBE-6016CF31A502@dilger.ca> (raw)
In-Reply-To: <20180601114151.GA25225@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 551 bytes --]
On Jun 1, 2018, at 7:41 AM, Christoph Hellwig <hch@infradead.org> wrote:
>
> Thanks,
>
> all that churn without much visible progress to a mergeable codebase
> was really ennoying.
>
> I'd recommend if people want to merge lustre they start with a managable
> subset first, e.g. the fs client code with simple IP-only networking.
Adding or removing the IB networking makes basically no difference to the
code size. This would also make the client much less useful, since a large
number of sites use Lustre with IB networks.
Cheers, Andreas
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 873 bytes --]
next prev parent reply other threads:[~2018-06-01 18:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 9:11 [PATCH] staging: lustre: delete the filesystem from the tree Greg Kroah-Hartman
2018-06-01 11:41 ` Christoph Hellwig
2018-06-01 18:20 ` Andreas Dilger [this message]
2018-06-01 18:25 ` [lustre-devel] " Doug Oucharek
2018-06-01 23:19 ` NeilBrown
2018-06-03 20:34 ` Dilger, Andreas
2018-06-04 3:54 ` NeilBrown
2018-06-04 3:59 ` Alexey Lyashkov
2018-06-04 4:15 ` Andreas Dilger
2018-06-04 4:17 ` Alexey Lyashkov
2018-06-01 18:30 ` Andreas Dilger
2018-06-01 18:41 ` Oleg Drokin
2018-06-01 19:08 ` Greg Kroah-Hartman
2018-06-04 7:09 ` Christoph Hellwig
2018-06-04 7:14 ` Greg Kroah-Hartman
2018-06-02 0:28 ` [lustre-devel] " NeilBrown
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=E5BF8501-35EB-4DDF-ADBE-6016CF31A502@dilger.ca \
--to=adilger@dilger.ca \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=jsimmons@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=oleg.drokin@intel.com \
--cc=selinux@tycho.nsa.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).