From: Kamil Rytarowski <n54@gmx.com>
To: Pedro Alves <palves@redhat.com>, John Baldwin <jhb@FreeBSD.org>,
gdb-patches@sourceware.org, coypu@sdf.org
Subject: Re: [PATCH v2 0/2] Various build fixes for NetBSD
Date: Mon, 04 Sep 2017 13:03:00 -0000 [thread overview]
Message-ID: <1ac94d76-8452-8fc7-b35f-b8186d4edaaa@gmx.com> (raw)
In-Reply-To: <4e0601ae-32eb-9e6a-1a64-df588e58a2c2@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 693 bytes --]
On 04.09.2017 14:50, Pedro Alves wrote:
> On 07/25/2017 05:50 PM, John Baldwin wrote:
>> Relative to the first patch series: one patch has been committed,
>> the amd64 KVM support has been dropped, the _KMEMUSER #define was
>> moved earlier in bsd-kvm.o, and the x86 debug registers change was
>> expanded to also add needed object files in the NetBSD/x86 native
>> targets. I haven't been able to test remaining patches so am
>> waiting for testing reports from coypu@.
>>
>
> This hasn't been pushed yet, right?
> FWIW, it looks good to me.
>
> Thanks,
> Pedro Alves
>
Hi,
NetBSD patches are still pending. I'm going to readd NetBSD buildbot
after merging them.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-09-04 13:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 16:51 John Baldwin
2017-07-25 16:51 ` [PATCH v2 1/2] Define _KMEMUSER before including BSD kernel headers John Baldwin
2017-07-25 16:51 ` [PATCH v2 2/2] Enable support for x86 debug registers on NetBSD John Baldwin
2017-09-04 12:50 ` [PATCH v2 0/2] Various build fixes for NetBSD Pedro Alves
2017-09-04 13:03 ` Kamil Rytarowski [this message]
2017-09-04 14:01 ` Pedro Alves
2017-09-04 14:34 ` Kamil Rytarowski
2017-09-04 17:08 ` John Baldwin
2017-09-04 13:27 ` John Baldwin
2017-09-04 20:04 ` coypu
2017-09-04 22:18 ` John Baldwin
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=1ac94d76-8452-8fc7-b35f-b8186d4edaaa@gmx.com \
--to=n54@gmx.com \
--cc=coypu@sdf.org \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.org \
--cc=palves@redhat.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