From: Tom Zanussi <tom.zanussi@intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: yocto@yoctoproject.org, "Osier-mixon,
Jeffrey" <jeffrey.osier-mixon@intel.com>
Subject: Re: example of Kernel work
Date: Wed, 06 Nov 2013 13:08:45 -0600 [thread overview]
Message-ID: <1383764925.3022.21.camel@empanada> (raw)
In-Reply-To: <alpine.DEB.2.02.1311061359570.6260@oneiric>
On Wed, 2013-11-06 at 14:02 -0500, Robert P. J. Day wrote:
> On Wed, 6 Nov 2013, Tom Zanussi wrote:
>
> ... snip ...
>
> > OK, well, anyway, until it gets fixed, here's a link to the pdf:
> >
> > https://www.yoctoproject.org/sites/yoctoproject.org/files/kernel-lab-1.4.pdf
> >
> > And here are the accompanying layers:
> >
> > https://www.yoctoproject.org/sites/yoctoproject.org/files/kernel-lab-1.4-layers.tar.bz2
> >
> > Sorry for the inconvenience.
>
> i recall exchanging some email with tom a few weeks back about that
> very lab. i started working through it and making notes as to how to
> update it for 1.5 so that i could use it in upcoming OE/yocto classes.
> my goal is for something that is based on his 1.4 lab but tweaked here
> and there to match the rest of my courseware.
>
> when i finally get it done, i'll post it -- unless tom updates his
> lab first. :-)
>
I do have the 1.5 update on my schedule for 1.6 M1, but if you were
going to do something like that anyway, that would be great. I wasn't
actually going to start on it until next week - I guess I should check
with you then before I actually start diving in...
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5486
Thanks,
Tom
> rday
>
prev parent reply other threads:[~2013-11-06 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 10:26 example of Kernel work John Whitmore
2013-11-06 14:00 ` Tom Zanussi
2013-11-06 14:12 ` Tom Zanussi
2013-11-06 18:30 ` John Whitmore
2013-11-06 19:02 ` Robert P. J. Day
2013-11-06 19:08 ` Tom Zanussi [this message]
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=1383764925.3022.21.camel@empanada \
--to=tom.zanussi@intel.com \
--cc=jeffrey.osier-mixon@intel.com \
--cc=rpjday@crashcourse.ca \
--cc=yocto@yoctoproject.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.