From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Darren Hart <dvhart@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: TODO Lists
Date: Tue, 17 May 2016 17:48:00 +0200 [thread overview]
Message-ID: <20160517154800.GA15536@kozik-lap> (raw)
In-Reply-To: <1462884977.17131.301.camel@linux.intel.com>
On Tue, May 10, 2016 at 03:56:17PM +0300, Andy Shevchenko wrote:
> On Fri, 2016-05-06 at 10:08 -0700, Darren Hart wrote:
> > At kernel summit Greg suggested sending our TODO lists to him. We'd
> > like to have
> > a place to keep a feature wishlist and cleanups that aren't "bugs"
> > that we can
> > update regularly and that is easy for people looking for work to find,
> > and that
> > people like Greg can readily refer to as well.
> >
> > Is there something already in place for this? It would be really nice
> > if there
> > was a common infrastructure. I suppose we could use the bugzilla, but
> > I think
> > I'd prefer that remained for actual bugs.
> >
> > Thanks,
> >
>
> Found this wiki page
> http://kernelnewbies.org/IIO_tasks
I store few tasks around Samsung here:
https://wiki.tizen.org/wiki/Exynos_Mainline_Kernel_TODO
Feel free to pass it further or edit.
The problem with generic lists is that you need a person with strong
ownership who will maintain it. Otherwise it will get abandoned over
time...
Best regards,
Krzysztof
next prev parent reply other threads:[~2016-05-17 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 17:08 TODO Lists Darren Hart
2016-05-10 12:56 ` Andy Shevchenko
2016-05-10 13:04 ` Shuah Khan
2016-05-17 15:48 ` Krzysztof Kozlowski [this message]
2016-05-17 18:17 ` Arnaldo Carvalho de Melo
2016-05-18 20:38 ` Darren Hart
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=20160517154800.GA15536@kozik-lap \
--to=k.kozlowski@samsung.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dvhart@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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.