From: Joe Perches <joe@perches.com>
To: James Simmons <jsimmons@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org,
Andreas Dilger <andreas.dilger@intel.com>,
Oleg Drokin <oleg.drokin@intel.com>, NeilBrown <neilb@suse.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lustre Development List <lustre-devel@lists.lustre.org>
Subject: Re: [PATCH] staging: lustre: update the TODO list
Date: Sun, 11 Feb 2018 15:16:01 -0800 [thread overview]
Message-ID: <1518390961.4139.1.camel@perches.com> (raw)
In-Reply-To: <1518390008-17876-1-git-send-email-jsimmons@infradead.org>
On Sun, 2018-02-11 at 18:00 -0500, James Simmons wrote:
> As more people become involved with the progression of the lustre
> client it needs to more clear what needs to be done to leave
> staging. Update the TODO list with the various bugs and changes
> to accomplish this. Some are simple bugs and others are far more
> complex task that will change many lines of code. Some even cover
> updating the user land utilities to meet the kernel requirements.
> Several bugs have already been addressed and just need to be
> pushed to the staging tree.
Nice list.
Are or should those entries that have been addressed
also in this new list?
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2018-02-11 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 23:00 James Simmons
2018-02-11 23:16 ` Joe Perches [this message]
2018-02-12 2:06 ` James Simmons
2018-02-12 3:21 ` 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=1518390961.4139.1.camel@perches.com \
--to=joe@perches.com \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=neilb@suse.com \
--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
Powered by JetHome