From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2020-11-02
Date: Tue, 03 Nov 2020 10:27:33 +0100 [thread overview]
Message-ID: <87sg9q94e2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <49-5fa11a00-1-271de3c0@117826441> (Michael Nosthoff via buildroot's message of "Tue, 03 Nov 2020 09:51:05 +0100")
>>>>> "Michael" == Michael Nosthoff via buildroot <buildroot@busybox.net> writes:
> Hi Peter,
> from time to time I get this build failure reported:
> On Tuesday, November 03, 2020 09:10 CET, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
>>
>> Results for the '2020.02.x' branch
>> ----------------------------------
>>
>> Build failures related to your packages:
>>
>> arch | reason | url
>> -------------+--------------------------------+---------------------------------------------------------------------------------
>> or1k | host-grpc-1.25.0 |
>> http://autobuild.buildroot.net/results/605a7e9911fac8785272d0ffdabdde9c8876daa5
>>
> this was fixed by this commit:
> https://patchwork.ozlabs.org/project/buildroot/patch/20200915161107.1826-1-buildroot at heine.tech/
> Would it make sense to pick this for LTS?
I think so - Committed to 2020.02.x and 2020.08.x, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2020-11-03 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 8:51 [Buildroot] [autobuild.buildroot.net] Your daily results for 2020-11-02 Michael Nosthoff
2020-11-03 9:27 ` Peter Korsgaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-03 10:30 Gwenhael Goavec-Merou
2020-11-03 18:35 ` Peter Korsgaard
[not found] <notmuch-sha1-b4794100ef702a3659a6eb92965001e8055c9c8c>
2020-11-11 14:46 ` Adrian Perez de Castro
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=87sg9q94e2.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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