From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: vapier@gentoo.org
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC 0/4] Fix recent sim/*/config.in fallout: frv, m32r, sh64, iq2000
Date: Tue, 24 Mar 2015 05:55:00 -0000 [thread overview]
Message-ID: <201503240555.t2O5tNBZ009203@ignucius.se.axis.com> (raw)
In-Reply-To: <20150324041856.GC10761@vapier> (message from Mike Frysinger on Tue, 24 Mar 2015 05:18:56 +0100)
> From: Mike Frysinger <vapier@gentoo.org>
> Date: Tue, 24 Mar 2015 05:18:56 +0100
> i've finished landing a series of changes into master that can be summarized:
> - clean up dv-sockser code to centralize its enabled/disabled logic
> - let the common code handle building of dv-sockser all the time (sans mingw)
> - fix bugs around SIM_AC_OPTION_HARDWARE default enable
> - delete the broken uart code from frv devices
Sounds good.
> that leads me back to this patch series. there's no longer a need to disable
> hw in these sims by default, so i've somewhat reverted these changes by setting
> the default to "yes" for them.
'k. FWIW, nothing broke for my autotester setup (targets likely
mentioned in the quoted post).
> testcases would certainly be nice, but i have no idea how to write ones for
> these ports. i'll be pestering people in the future when they make updates to
> specific arches, and i'll be rejecting new sims that lack any tests.
Good! :)
brgds, H-P
next prev parent reply other threads:[~2015-03-24 5:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 4:28 Hans-Peter Nilsson
2014-08-23 3:13 ` Hans-Peter Nilsson
2015-03-24 4:18 ` Mike Frysinger
2015-03-24 5:55 ` Hans-Peter Nilsson [this message]
2015-03-24 4:19 ` [PATCH] sim: Revert "Fix frv/iq2000/m32r/sh64 sim, default hardware to off." Mike Frysinger
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=201503240555.t2O5tNBZ009203@ignucius.se.axis.com \
--to=hans-peter.nilsson@axis.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.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