All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Till Kamppeter <till.kamppeter@gmail.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Google Summer of Code 2011 - Wireless application
Date: Wed, 13 Apr 2011 21:49:35 +0200	[thread overview]
Message-ID: <1302724175.3731.17.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4DA5FAF9.3090309@gmail.com>

On Wed, 2011-04-13 at 21:35 +0200, Till Kamppeter wrote:

> If you are not interested at all, please tell me ASAP so that I can 
> simply reject the applications on your behalf.

I won't have time to mentor anyone this year.


I do note, however, that the projects aren't really very well thought
out.

The IBSS one is concerned with TPT but somebody else is working on 11n
support anyway, for instance. Also multiple IBSS per HW, which is really
tricky and can only work in corner cases. Overall, I'm not convinced
this is a suitable project.

The second one is just totally useless.

The last one looks a bit like some googling around the problem space of
a basic idea ("improve roaming"), but offers no reasonable indication as
to actually achieving any type of solution, and any actual roaming
improvements wouldn't be in the kernel anyway.

Even if I had time to mentor, I think I'd reject these applications
anyway.

johannes


      reply	other threads:[~2011-04-13 19:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13 19:35 Google Summer of Code 2011 - Wireless application Till Kamppeter
2011-04-13 19:49 ` Johannes Berg [this message]

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=1302724175.3731.17.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --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 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.