From: Mark Gross <mgross@linux.intel.com>
To: Rik van Riel <riel@surriel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: WANTED: kernel projects for CS students
Date: Mon, 15 Oct 2007 10:04:11 -0700 [thread overview]
Message-ID: <20071015170411.GB18550@linux.intel.com> (raw)
In-Reply-To: <20071014190128.6e3cdb44@bree.surriel.com>
On Sun, Oct 14, 2007 at 07:01:28PM -0400, Rik van Riel wrote:
> The kernel newbies community often gets inquiries from CS students who
> need a project for their studies and would like to do something with
> the Linux kernel, but would also like their code to be useful to the
> community afterwards.
>
> In order to make it easier for them, I am trying to put together a
> page with projects that:
> - Are self contained enough that the students can implement the
> project by themselves, since that is often a university requirement.
> - Are self contained enough that Linux could merge the code (maybe
> with additional changes) after the student has been working on it
> for a few months.
> - Are large enough to qualify as a student project, luckily there is
> flexibility here since we get inquiries for anything from 6 week
> projects to 6 month projects.
>
> If you have ideas on what projects would be useful, please add them
> to this page (or email me):
>
> http://kernelnewbies.org/KernelProjects
Is there already a make config option that will do a good job at setting
a default .config file based on what is already running on a system?
I get tiered of trimming down my .config for my laptop build so it takes
less than 30min to build a kernel.
Bonus credit to additional "expert" options (like those powertop puts
out) for target uses, laptop, HPC, home file share, embedded targets....
Oh, and lets make the expert configs easily extensible.
--mgross
>
> thanks,
>
> Rik
> --
> "Debugging is twice as hard as writing the code in the first place.
> Therefore, if you write the code as cleverly as possible, you are,
> by definition, not smart enough to debug it." - Brian W. Kernighan
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2007-10-15 17:11 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 23:01 WANTED: kernel projects for CS students Rik van Riel
2007-10-15 10:40 ` WANG Cong
2007-10-15 17:13 ` Rik van Riel
2007-10-15 14:23 ` Sam Ravnborg
2007-10-15 15:10 ` Rik van Riel
2007-10-15 18:31 ` Sam Ravnborg
2007-10-15 16:31 ` Philippe Elie
2007-10-15 16:36 ` Philippe Elie
2007-10-15 16:52 ` Jan Engelhardt
2007-10-15 16:53 ` Xavier Bestel
2007-10-15 18:19 ` Sam Ravnborg
2007-10-15 15:40 ` Jörn Engel
2007-10-15 17:04 ` Doug Whitesell (LKML)
2007-10-15 17:04 ` Mark Gross [this message]
2007-10-15 18:30 ` Sam Ravnborg
2007-10-15 18:45 ` Mark Gross
2007-10-15 19:54 ` Giacomo Catenazzi
2007-10-16 20:06 ` Mark Gross
2007-10-16 20:09 ` Jan Engelhardt
2007-10-16 20:23 ` Rik van Riel
2007-10-16 20:25 ` Jan Engelhardt
2007-10-16 21:10 ` david
2007-10-16 21:30 ` david
2007-11-02 7:54 ` Giacomo Catenazzi
2007-10-16 20:31 ` Giacomo Catenazzi
2007-10-15 19:17 ` Alexey Dobriyan
2007-10-15 19:54 ` Folkert van Heusden
2007-10-16 20:10 ` Mark Gross
2007-10-16 0:39 ` david
2007-10-15 17:10 ` Zan Lynx
2007-10-15 17:23 ` Rik van Riel
2007-10-16 0:51 ` david
2007-10-15 17:30 ` Guilherme Amadio
2007-10-15 18:03 ` J. Bruce Fields
2007-10-17 17:45 ` Mark Gross
2007-10-18 4:51 ` Toshiharu Harada
2007-10-28 18:07 ` Pavel Machek
2007-10-28 18:57 ` Rafael J. Wysocki
2007-10-29 19:48 ` Lennart Sorensen
2007-10-29 20:19 ` Pavel Machek
2007-10-29 21:44 ` Lennart Sorensen
2007-11-03 3:08 ` Valdis.Kletnieks
2007-11-03 3:36 ` Rik van Riel
2007-11-03 9:44 ` Wander Winkelhorst
2007-11-03 10:05 ` david
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=20071015170411.GB18550@linux.intel.com \
--to=mgross@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@surriel.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