From: Kevin Hilman <khilman@linaro.org> To: linux-arm-kernel <linux-arm-kernel@lists.infradead.org> Cc: arm-summit-discuss@lists.infradead.org, LKML <linux-kernel@vger.kernel.org>, linaro-kernel@lists.linaro.org Subject: [ANNOUNCE] ARM kernel mini-summit @ ELC: Call for Topics, Invitation Request Date: Thu, 13 Mar 2014 15:38:05 -0700 [thread overview] Message-ID: <7hmwgtk9ma.fsf@paris.lan> (raw) Hello, We will be holding a one-day, ARM kernel mini-summit at ELC this year in San Jose[1]. The mini-summit will be Monday, April 28th, and ELC starts on Tuesday. The ARM summit brings together maintainers and developers in the ARM community face to face to discuss current work and to plan for what is coming next. To keep the group small and encourage open discussion the event is invite-only. To propose a discussion topic and/or request an invitation: 1) subscribe yourself to arm-summit-discuss@lists.infradead.org: http://lists.infradead.org/mailman/listinfo/arm-summit-discuss 2) send your invite request and/or topic proposal to arm-summit-discuss@lists.infradead.org with a subject prefix of "[ARM ATTEND]". Also, please Cc the main linux-arm-kernel list. All topics and invitation requests will be reviewed by the program committee and decisions will be made by the end of March, so please get your requests/topics in soon. ARM mini-summit Program Committee, Arnd Bergmann Magnus Damm Kevin Hilman Simon Horman Olof Johansson Grant Likely [1] http://events.linuxfoundation.org/events/embedded-linux-conference
WARNING: multiple messages have this Message-ID (diff)
From: khilman@linaro.org (Kevin Hilman) To: linux-arm-kernel@lists.infradead.org Subject: [ANNOUNCE] ARM kernel mini-summit @ ELC: Call for Topics, Invitation Request Date: Thu, 13 Mar 2014 15:38:05 -0700 [thread overview] Message-ID: <7hmwgtk9ma.fsf@paris.lan> (raw) Hello, We will be holding a one-day, ARM kernel mini-summit at ELC this year in San Jose[1]. The mini-summit will be Monday, April 28th, and ELC starts on Tuesday. The ARM summit brings together maintainers and developers in the ARM community face to face to discuss current work and to plan for what is coming next. To keep the group small and encourage open discussion the event is invite-only. To propose a discussion topic and/or request an invitation: 1) subscribe yourself to arm-summit-discuss at lists.infradead.org: http://lists.infradead.org/mailman/listinfo/arm-summit-discuss 2) send your invite request and/or topic proposal to arm-summit-discuss at lists.infradead.org with a subject prefix of "[ARM ATTEND]". Also, please Cc the main linux-arm-kernel list. All topics and invitation requests will be reviewed by the program committee and decisions will be made by the end of March, so please get your requests/topics in soon. ARM mini-summit Program Committee, Arnd Bergmann Magnus Damm Kevin Hilman Simon Horman Olof Johansson Grant Likely [1] http://events.linuxfoundation.org/events/embedded-linux-conference
next reply other threads:[~2014-03-13 22:38 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-03-13 22:38 Kevin Hilman [this message] 2014-03-13 22:38 ` [ANNOUNCE] ARM kernel mini-summit @ ELC: Call for Topics, Invitation Request Kevin Hilman 2014-03-22 18:07 ` Olof Johansson 2014-03-22 18:07 ` Olof Johansson
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=7hmwgtk9ma.fsf@paris.lan \ --to=khilman@linaro.org \ --cc=arm-summit-discuss@lists.infradead.org \ --cc=linaro-kernel@lists.linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@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: linkBe 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.