From: Adrian Bunk <bunk@stusta.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3] ofono: upgrade 1.25 -> 1.29
Date: Tue, 21 May 2019 14:45:02 +0300 [thread overview]
Message-ID: <20190521114502.GA25364@localhost> (raw)
In-Reply-To: <3271f12b90cabf68ba0a2223b48aaf24b723d79e.camel@linuxfoundation.org>
On Tue, May 21, 2019 at 11:42:04AM +0100, Richard Purdie wrote:
> On Thu, 2019-05-16 at 11:56 +0300, Adrian Bunk wrote:
> > Remove patch applied upstream.
> > Backport two fixes for build failures
> >
> > Signed-off-by: Adrian Bunk <bunk@stusta.de>
> > ---
> > v3: Another buildfix backported.
>
> I merged this but it seems there are still some other races in there
> which appeared in later builds:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/67/builds/612
Fix sent.
> Cheers,
>
> Richard
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-05-21 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 8:56 [PATCH v3] ofono: upgrade 1.25 -> 1.29 Adrian Bunk
2019-05-21 10:42 ` Richard Purdie
2019-05-21 11:45 ` 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=20190521114502.GA25364@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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