From: Adrian Bunk <bunk@stusta.de>
To: Armin Kuster <akuster808@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [thud][PATCH 0/9] Fixes for Thud
Date: Wed, 29 May 2019 17:11:16 +0300 [thread overview]
Message-ID: <20190529141116.GC28892@localhost> (raw)
In-Reply-To: <1559137838-8972-1-git-send-email-akuster808@gmail.com>
On Wed, May 29, 2019 at 06:50:29AM -0700, Armin Kuster wrote:
>..
> Mingli Yu (2):
> nettle: fix ptest failure
>...
> Richard Purdie (1):
> Revert "nettle: fix ptest failure"
>...
These should be dropped for obvious reasons.
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
next prev parent reply other threads:[~2019-05-29 14:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 13:50 [thud][PATCH 0/9] Fixes for Thud Armin Kuster
2019-05-29 13:50 ` [thud][PATCH 1/9] glibc: Security fix CVE-2019-9169 Armin Kuster
2019-05-29 13:50 ` [thud][PATCH 2/9] elfutils: Security fixes CVE-2019-7146, 7149, 7150 Armin Kuster
2019-05-29 13:50 ` [thud][PATCH 3/9] gnutls: no need to inherit binconfig Armin Kuster
2019-05-29 14:10 ` Adrian Bunk
2019-05-29 13:50 ` [thud][PATCH 4/9] gnutls: update to 3.6.5 Armin Kuster
2019-05-29 14:08 ` Adrian Bunk
2019-05-29 13:50 ` [thud][PATCH 5/9] gnutls: upgrade 3.6.5 -> 3.6.7 Armin Kuster
2019-05-29 13:50 ` [thud][PATCH 6/9] nettle: update to 3.4.1 Armin Kuster
2019-05-29 13:50 ` [thud][PATCH 7/9] nettle: fix ptest failure Armin Kuster
2019-05-29 13:50 ` [thud][PATCH 8/9] Revert "nettle: fix ptest failure" Armin Kuster
2019-05-29 13:50 ` [thud][PATCH 9/9] nettle: fix the Segmentation fault Armin Kuster
2019-05-29 14:11 ` Adrian Bunk [this message]
2019-06-01 15:45 ` [thud][PATCH 0/9] Fixes for Thud akuster808
2019-06-01 16:00 ` Adrian Bunk
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=20190529141116.GC28892@localhost \
--to=bunk@stusta.de \
--cc=akuster808@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