From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Till Kamppeter <till.kamppeter@gmail.com>,
Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org,
lsb-discuss@lists.linux-foundation.org,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Subject: Re: Linux wireless GSoC 2010 project ideas
Date: Thu, 28 Jan 2010 15:23:15 -0800 [thread overview]
Message-ID: <43e72e891001281523s56707279x896ab059e6d4e530@mail.gmail.com> (raw)
In-Reply-To: <20100128231545.GH18683@nowhere>
On Thu, Jan 28, 2010 at 3:15 PM, Frederic Weisbecker <fweisbec@gmail.com> wrote:
> I'm sorry if I'm a bit off-topic. But as I see this announce,
> I'm wondering about the topics for the google summer of code
> in the wider scope of the entire kernel.
>
> I'm a student and there are fair chances I'll be free for this
> summer so I start to think about applying.
>
> Are there currently some plans concerning other kernel areas?
These would be under the Linux Foundation umbrella, the wireless stuff
I just posted is just for wireless. I do not believe we have a common
forum yet for general linux stuff. Till?
> That doesn't mean I wouldn't be interested in a wireless project :)
> but there are many other areas that could host a Gsoc project too
> and I don't want to miss the whole variety of proposals.
The LF projects will be posted on the LF site.
> I guess we also can, as applying students, propose subjects too.
> Provided we find a mentor for the given project, which makes the
> things harder in this direction I fear.
I don't see why not.
> Anyway, what would be the right place to submit such proposals? I
> have various ideas in mind, in topics such as tracing/profiling,
> realtime, among other things... (could be: "Do as much bkl bashing
> as you can in two months, have fun, be brave...").
I'll let Till answer :D
Luis
next prev parent reply other threads:[~2010-01-28 23:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 21:38 Linux wireless GSoC 2010 project ideas Luis R. Rodriguez
2010-01-28 22:06 ` Till Kamppeter
2010-01-28 22:14 ` Luis R. Rodriguez
2010-02-04 4:52 ` Hin-Tak Leung
2010-01-28 23:15 ` Frederic Weisbecker
2010-01-28 23:23 ` Luis R. Rodriguez [this message]
2010-01-28 23:31 ` Greg KH
2010-01-28 23:41 ` Frederic Weisbecker
2010-01-28 23:51 ` Till Kamppeter
2010-03-09 22:43 ` Frederic Weisbecker
2010-03-12 8:12 ` Till Kamppeter
2010-03-18 3:40 ` Frederic Weisbecker
2010-03-12 8:59 ` Till Kamppeter
2010-03-12 9:38 ` [lsb-discuss] " Denis Silakov
2010-03-12 9:57 ` Till Kamppeter
2010-03-21 19:49 ` Frederic Weisbecker
2010-01-31 21:03 ` Witold Sowa
2010-01-31 21:20 ` Johannes Berg
2010-02-01 18:01 ` Luis R. Rodriguez
2010-02-01 20:14 ` Maxim Levitsky
2010-02-01 20:17 ` david
2010-02-01 21:31 ` Maxim Levitsky
2010-02-03 9:23 ` Holger Schurig
2010-02-01 22:12 ` Nick Bowler
2010-02-02 4:25 ` Pat Erley
2010-02-03 9:25 ` Holger Schurig
2010-02-22 21:25 ` Luis R. Rodriguez
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=43e72e891001281523s56707279x896ab059e6d4e530@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=fweisbec@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lsb-discuss@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=till.kamppeter@gmail.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;
as well as URLs for NNTP newsgroup(s).