mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Simmons <jsimmons@infradead.org>
To: Joe Perches <joe@perches.com>
Cc: devel@driverdev.osuosl.org,
	Andreas Dilger <andreas.dilger@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	NeilBrown <neilb@suse.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Oleg Drokin <oleg.drokin@intel.com>,
	Lustre Development List <lustre-devel@lists.lustre.org>
Subject: Re: [PATCH] staging: lustre: update the TODO list
Date: Mon, 12 Feb 2018 02:06:07 +0000 (GMT)	[thread overview]
Message-ID: <alpine.LFD.2.21.1802120158500.3291@casper.infradead.org> (raw)
In-Reply-To: <1518390961.4139.1.camel@perches.com>


> 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.

Thanks. Its nice to have a direction :-)

> Are or should those entries that have been addressed
> also in this new list?

Do you mean by those entries what originally was in the
TODO list or what has been fixed over the last 2 years?
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

  reply	other threads:[~2018-02-12  2:06 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
2018-02-12  2:06   ` James Simmons [this message]
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=alpine.LFD.2.21.1802120158500.3291@casper.infradead.org \
    --to=jsimmons@infradead.org \
    --cc=andreas.dilger@intel.com \
    --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=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
all inboxes | Powered by JetHome®