From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: wireless workshop coming soon :-)
Date: Fri, 01 Mar 2019 12:11:54 +0100 [thread overview]
Message-ID: <871s3qn91h.fsf@toke.dk> (raw)
In-Reply-To: <f90f210372b8c7f7efae0c43ab3ae925c334bc0e.camel@sipsolutions.net>
Johannes Berg <johannes@sipsolutions.net> writes:
> Please add your favourite topics to
>
> https://wireless.wiki.kernel.org/en/developers/summits/prague-2019
>
> I've added a few I think we should discuss at this stage, so also see if
> you have an opinion on those :-)
Cool! Could we schedule the scheduling and airtime fairness topics after
10:30? Have a tutorial to run in the morning and would obviously like to
participate in those discussions ;)
-Toke
next prev parent reply other threads:[~2019-03-01 11:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 10:49 wireless workshop coming soon :-) Johannes Berg
2019-03-01 11:11 ` Toke Høiland-Jørgensen [this message]
2019-03-01 11:12 ` Johannes Berg
2019-03-01 11:23 ` Toke Høiland-Jørgensen
2019-03-11 3:21 ` Kevin Hayes
2019-03-15 9:20 ` Johannes Berg
2019-03-15 9:21 ` Johannes Berg
2019-03-15 13:06 ` Toke Høiland-Jørgensen
2019-03-12 18:47 ` Kirtika Ruchandani
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=871s3qn91h.fsf@toke.dk \
--to=toke@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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.