From: Steven Rostedt <rostedt@goodmis.org>
To: Julia Cartwright <julia@ni.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>
Subject: Re: [CFP] RT Users Micro-Conf at Linux Plumbers 2017
Date: Tue, 28 Feb 2017 16:52:36 -0500 [thread overview]
Message-ID: <20170228165236.57ca19dd@gandalf.local.home> (raw)
In-Reply-To: <20170228214012.GP1733@jcartwri.amer.corp.natinst.com>
On Tue, 28 Feb 2017 15:40:12 -0600
Julia Cartwright <julia@ni.com> wrote:
> > I think a badge would still be worth purchasing. Having the ability to
> > help influence development is a worthy goal.
>
> I didn't mean to make it sound like I didn't consider the LPC badge to
> be worth it. LPC is one of my favorite conferences to attend! Anyone
> who asks me which Linux conferences to attend, LPC is always top on my
> list.
No worries, I didn't take it that way.
>
> However, from my experience, the attendees at LPC are largely already
> kernel engineers, or other low-level usermode people. I suppose it's a
> question of what "users" you are looking for.
Actually, we are trying to have LPC be more cross the board and not so
kernel centric. More like the old days of OLS.
>
> That doesn't necessarily include people who are domain-experts in RTOS
> applications but are relatively new to Linux; or people who use a
> distro-packaged RT kernels for professional audio but have run into a
> few minor snags; or ...
I think these people would be perfect for LPC!
> > I rather have you tell us were you want to help :)
>
> I'd happily talk to/facilitate discussions on the topics I mentioned
> above.
Hopefully we can get more people to reply to this. It would be useless
to have a Micro-Conf that consists of two people sharing war stories.
-- Steve
next prev parent reply other threads:[~2017-02-28 22:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 22:25 [CFP] RT Users Micro-Conf at Linux Plumbers 2017 Steven Rostedt
2017-02-28 20:41 ` Julia Cartwright
2017-02-28 21:04 ` Steven Rostedt
2017-02-28 21:40 ` Julia Cartwright
2017-02-28 21:52 ` Steven Rostedt [this message]
[not found] ` <CAFTL4hy7GtKkD7AAwPP72oNeGAGg4FLMJkaTv80CJkqpY3xehw@mail.gmail.com>
2017-03-02 2:08 ` Steven Rostedt
2017-03-02 14:10 ` Staffan Tjernstrom
2017-03-08 12:57 ` Frederic Weisbecker
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=20170228165236.57ca19dd@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=julia@ni.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.