From: Ross Burton <ross.burton@intel.com>
To: Christopher Larson <kergoth@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCHv2 6/6] psplash: add systemd support
Date: Fri, 20 Nov 2015 15:23:07 +0000 [thread overview]
Message-ID: <564F3ADB.7040000@intel.com> (raw)
In-Reply-To: <CABcZAN=HG8AJCjWHWTwWGs4vswnEL=SRF81fZz5r+iE+iQZ76g@mail.gmail.com>
On 18/11/2015 02:03, Christopher Larson wrote:
> Interesting, is psplash configured in our test environment? Either way,
> worst case we can drop this commit for now and can revisit it. I'm
> heading out of town tomorrow until December 1st, so likely will be
> limited in what I can do to address any issues that crop up during that
> period. Thanks.
It should be working - at least the sysvinit images work absolutely fine
and show the splash. I'll add giving this a go locally to my list of
things to do.
Ross
next prev parent reply other threads:[~2015-11-20 18:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 23:10 [PATCHv2 0/6] Misc improvements 1 from Mentor Christopher Larson
2015-11-13 23:10 ` [PATCHv2 1/6] image_types: improve wks path specification Christopher Larson
2015-11-13 23:10 ` [PATCHv2 2/6] sysprof: use packageconfig for the gui Christopher Larson
2015-11-13 23:10 ` [PATCHv2 3/6] sysprof: add missing gdk-pixbuf/pango deps Christopher Larson
2015-11-16 15:12 ` Burton, Ross
2015-11-16 15:55 ` Christopher Larson
2015-11-13 23:10 ` [PATCHv2 4/6] systemd: for valgrind, define VALGRIND=1 Christopher Larson
2015-11-13 23:10 ` [PATCHv2 5/6] bluez5: enable sysvinit support Christopher Larson
2015-11-13 23:10 ` [PATCHv2 6/6] psplash: add systemd support Christopher Larson
2015-11-17 21:36 ` Burton, Ross
2015-11-18 2:03 ` Christopher Larson
2015-11-20 15:23 ` Ross Burton [this message]
2015-12-08 15:38 ` Christopher Larson
2015-12-08 17:15 ` Otavio Salvador
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=564F3ADB.7040000@intel.com \
--to=ross.burton@intel.com \
--cc=kergoth@gmail.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox