From: Adrian Bunk <bunk@stusta.de>
To: Joe Slater <joe.slater@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] slang: modify an array test
Date: Thu, 6 Jun 2019 18:35:09 +0300 [thread overview]
Message-ID: <20190606153509.GB26324@localhost> (raw)
In-Reply-To: <20190605225040.213296-1-joe.slater@windriver.com>
On Wed, Jun 05, 2019 at 03:50:40PM -0700, Joe Slater wrote:
> One array test attempts to create an array that is far too
> large to exist. Different exceptions are thrown for 32 and 64
> bit machines, so we account for that when catching them.
>
> Signed-off-by: Joe Slater <joe.slater@windriver.com>
> ---
> meta/recipes-extended/slang/slang/array_test.patch | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>...
This seems to miss actually applying the patch?
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2019-06-06 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 22:50 [PATCH 1/1] slang: modify an array test Joe Slater
2019-06-06 15:35 ` Adrian Bunk [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=20190606153509.GB26324@localhost \
--to=bunk@stusta.de \
--cc=joe.slater@windriver.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