From: "Naveen Saini" <naveen.kumar.saini@intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Trevor Woerner <twoerner@gmail.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: Ross Burton <ross.burton@arm.com>, Jon Mason <Jon.Mason@arm.com>
Subject: Re: [OE-core] [master-next][PATCH 1/3] PSPLASH_FIFO_DIR: refactor
Date: Thu, 31 Dec 2020 07:55:08 +0000 [thread overview]
Message-ID: <2ef921246adf4a5eace5ccb72294ef82@intel.com> (raw)
In-Reply-To: <fbcefecc76d5cd481c661b57f0d394520ff646a3.camel@linuxfoundation.org>
> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Richard Purdie
> Sent: Wednesday, December 30, 2020 10:10 PM
> To: Trevor Woerner <twoerner@gmail.com>; openembedded-
> core@lists.openembedded.org
> Cc: Ross Burton <ross.burton@arm.com>; Jon Mason
> <Jon.Mason@arm.com>; Saini, Naveen Kumar
> <naveen.kumar.saini@intel.com>
> Subject: Re: [OE-core] [master-next][PATCH 1/3] PSPLASH_FIFO_DIR:
> refactor
>
> On Thu, 2020-12-24 at 10:31 -0500, Trevor Woerner wrote:
> > Add an entry for the psplash fifo directory to /etc/default/rcS and
> > have the pieces of code that need it source it from there rather than
> > duplicating the definition in multiple places throughout the code.
> >
> > Signed-off-by: Trevor Woerner <twoerner@gmail.com>
> > ---
> > meta/recipes-core/psplash/files/psplash-init | 4 +++-
> > meta/recipes-core/sysvinit/sysvinit/rc | 5 +++--
> > meta/recipes-core/sysvinit/sysvinit/rcS-default | 2 ++
> > 3 files changed, 8 insertions(+), 3 deletions(-)
>
> Unfortunately this doesn't seem to build on arm hosts, something to do with
> the fifo I'd guess, e.g.:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/97/builds/2179
>
> I've not looked any further due to holidays but this probably needs a bugzilla
> entry and further investigation. Series is on hold until we get to the bottom
> of this.
[SWAT] https://bugzilla.yoctoproject.org/show_bug.cgi?id=14173
>
> Cheers,
>
> Richard
>
>
prev parent reply other threads:[~2020-12-31 7:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 15:31 [master-next][PATCH 1/3] PSPLASH_FIFO_DIR: refactor Trevor Woerner
2020-12-24 15:31 ` [master-next][PATCH 2/3] psplash: fix working on first boot (sysvinit) Trevor Woerner
2020-12-24 15:31 ` [master-next][PATCH 3/3] psplash (sysvinit): add textual updates Trevor Woerner
2020-12-30 14:10 ` [OE-core] [master-next][PATCH 1/3] PSPLASH_FIFO_DIR: refactor Richard Purdie
2020-12-31 7:55 ` Naveen Saini [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=2ef921246adf4a5eace5ccb72294ef82@intel.com \
--to=naveen.kumar.saini@intel.com \
--cc=Jon.Mason@arm.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@arm.com \
--cc=twoerner@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