ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	Grant Likely <grant.likely@secretlab.ca>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] KSummit workshop schedule
Date: Tue, 5 Sep 2017 13:57:45 +0200	[thread overview]
Message-ID: <94a12cfa-846e-718e-a49e-02be9d12168c@suse.cz> (raw)
In-Reply-To: <20170905111543.GA521@jagdpanzerIV.localdomain>

On 09/05/2017 01:15 PM, Sergey Senozhatsky wrote:
> On (09/05/17 10:20), Grant Likely wrote:
> [..]
>> I posted an update to the devicetree-spec list. This workshop has been
>> scheduled. It will be Thursday afternoon, 26 October. Attendees need
>> to be registered for OSSE/ELCE to attend, or be invited to the Kernel
>> Maintainers Summit.
>>
>> Now I need to pull together an agenda.
>>
>> Keep an eye on this wiki page for details:
>>
>> http://wiki.linuxplumbersconf.org/2017:device_tree
> 
> thanks! got it.
> 
> 
> p.s.
> wondering if there is some sort of "KSummit workshop schedule"
> available anywhere.

Hi,

I only found this:

http://events.linuxfoundation.org/events/linux-kernel-summit/program/about

Vlastimil

> 	-ss
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
> 

  reply	other threads:[~2017-09-05 11:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-28 12:44 Grant Likely
2017-09-05  4:38 ` Sergey Senozhatsky
2017-09-05  9:20   ` Grant Likely
2017-09-05 11:15     ` Sergey Senozhatsky
2017-09-05 11:57       ` Vlastimil Babka [this message]
2017-09-05 12:58         ` Sergey Senozhatsky

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=94a12cfa-846e-718e-a49e-02be9d12168c@suse.cz \
    --to=vbabka@suse.cz \
    --cc=grant.likely@secretlab.ca \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=sergey.senozhatsky.work@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox