All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	"Marcel Holtmann" <marcel@holtmann.org>,
	"Larry Finger" <Larry.Finger@lwfinger.net>,
	"Matt Chen" <machen@suse.com>, joeyli <jlee@suse.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Linux summit this year ?
Date: Sat, 4 May 2013 23:28:29 +0200	[thread overview]
Message-ID: <51857D7D.3010706@broadcom.com> (raw)
In-Reply-To: <1367592778.13104.37.camel@jlt4.sipsolutions.net>

On 05/03/2013 04:52 PM, Johannes Berg wrote:
> On Fri, 2013-05-03 at 10:49 -0400, John W. Linville wrote:
>
>>> Sounds good to me. If it overlaps LPC, which one are people going to
>>> have to register for (if not going to both anyway)?
>>
>> I would presume that if you want to got to LPC sessions then you
>> would have to register for LPC.  Generally we have required Wireless
>> Summit attendees to register for LinuxCon, and I presume that would
>> be required this time (so both LinuxCon and LPC if you want the
>> LPC sessions).
>
> That's what I figured, would just be good to announce it (you're going
> to send an invitation email once plans are finalized, right? :) )
>
>> Alternatively, probably we could have a separate Wireless Summit
>> registration -- not sure what that will cost, but it probably won't
>> be zero.
>
> That seems far too much overhead, and people who are there likely want
> to attend some other sessions anyway.
>
>> Probably can have an easel w/ a big note pad
>
> Sure, that's almost equivalent and much easier I guess. No need to
> inquire otherwise.

So the wl summit is going to be in North-America this year? I was 
setting my hopes on Edinburgh.

Gr. AvS


  reply	other threads:[~2013-05-04 21:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CALx5=V-wOkHb1Q4A_32LBQm9aP0dUL1J5s4ceLwqVGSYhfpwxw@mail.gmail.com>
2013-02-25 14:32 ` Linux summit this year ? John W. Linville
2013-02-25 16:29   ` Marcel Holtmann
2013-02-25 18:34     ` Larry Finger
2013-02-25 21:12       ` John W. Linville
2013-02-25 23:27         ` John W. Linville
2013-02-26 15:21         ` Marcel Holtmann
2013-05-02 19:27           ` Johannes Berg
2013-05-02 19:43             ` John W. Linville
2013-05-03  8:11               ` Johannes Berg
2013-05-03 14:49                 ` John W. Linville
2013-05-03 14:52                   ` Johannes Berg
2013-05-04 21:28                     ` Arend van Spriel [this message]
2013-05-05 12:26                       ` John W. Linville
2013-05-07 16:42                   ` Seth Forshee
2013-05-07 17:44                     ` John W. Linville
2013-05-08 13:20                       ` Seth Forshee
2013-05-08 15:09                       ` John W. Linville
     [not found]                         ` <CALx5=V_4LOmZ=dkhtKmZ3FdgzEq6t4jSBogzoPn+KyFTBZ6Zvw@mail.gmail.com>
2013-05-13 14:07                           ` John W. Linville
2013-05-07 18:30                     ` Marcel Holtmann
2013-03-04 15:53         ` Johannes Berg
2013-05-22 17:18 ` [linux-nfc] Linux wireless summit, 19-20 September 2013 in New Orleans! John W. Linville
2013-05-22 17:18   ` John W. Linville

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=51857D7D.3010706@broadcom.com \
    --to=arend@broadcom.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=jlee@suse.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=machen@suse.com \
    --cc=marcel@holtmann.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.