From: Peter Maydell <peter.maydell@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Ákos Kovács" <akoskovacs@gmx.com>,
"Anthony Liguori" <anthony@codemonkey.ws>,
"Patch Tracking" <patches@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v2 0/4] avoid CONFIG_NO_* using rules.mak logic/string fns
Date: Fri, 27 Sep 2013 12:02:58 +0900 [thread overview]
Message-ID: <CAFEAcA8fOJQxVFyvMjnd30274iRcLr+9dCa1QmKOTpc2XNXVbA@mail.gmail.com> (raw)
In-Reply-To: <1379093154-11348-1-git-send-email-peter.maydell@linaro.org>
Ping!
thanks
-- PMM
On 14 September 2013 02:25, Peter Maydell <peter.maydell@linaro.org> wrote:
> This is based on a set of patches by Ákos Kovács which were
> lurking at the beginning of his KConfig patchset but which
> I think make a nice standalone cleanup. Since I basically
> rewrote all of patch 1&2 in review comments I figured it was
> easier to just write it as a new patch. Patch 3 and 4
> are Ákos', though I fixed a few missed conversions in patch 3.
>
> Changes v1->v2:
> * split into a patch for logic functions and one for string fns
> * at Paolo's suggestion, renamed the 'n' == '' comparisons
> as 'leqv' and 'lxor', and reintroduced Ákos' string compares
> as eq/ne
> * added back in lif, which I'd accidentally left out of
> patch 1
>
> Peter Maydell (2):
> rules.mak: New logical functions for handling y/n values
> rules.mak: New string testing functions
>
> Ákos Kovács (2):
> Makefile.target: CONFIG_NO_* variables removed
> default-configs/: CONFIG_GDBSTUB_XML removed
>
> Makefile.target | 10 +++-------
> default-configs/arm-linux-user.mak | 2 --
> default-configs/arm-softmmu.mak | 1 -
> default-configs/armeb-linux-user.mak | 2 --
> default-configs/m68k-linux-user.mak | 2 --
> default-configs/m68k-softmmu.mak | 1 -
> default-configs/ppc-linux-user.mak | 2 --
> default-configs/ppc-softmmu.mak | 1 -
> default-configs/ppc64-linux-user.mak | 2 --
> default-configs/ppc64-softmmu.mak | 1 -
> default-configs/ppc64abi32-linux-user.mak | 2 --
> default-configs/ppcemb-softmmu.mak | 1 -
> hw/pci/Makefile.objs | 2 +-
> rules.mak | 28 ++++++++++++++++++++++++++++
> target-arm/Makefile.objs | 2 +-
> target-i386/Makefile.objs | 2 +-
> target-ppc/Makefile.objs | 2 +-
> 17 files changed, 35 insertions(+), 28 deletions(-)
>
> --
> 1.7.9.5
>
>
next prev parent reply other threads:[~2013-09-27 3:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 17:25 [Qemu-devel] [PATCH v2 0/4] avoid CONFIG_NO_* using rules.mak logic/string fns Peter Maydell
2013-09-13 17:25 ` [Qemu-devel] [PATCH v2 1/4] rules.mak: New logical functions for handling y/n values Peter Maydell
2013-09-13 17:25 ` [Qemu-devel] [PATCH v2 2/4] rules.mak: New string testing functions Peter Maydell
2013-09-13 17:25 ` [Qemu-devel] [PATCH v2 3/4] Makefile.target: CONFIG_NO_* variables removed Peter Maydell
2013-09-13 17:25 ` [Qemu-devel] [PATCH v2 4/4] default-configs/: CONFIG_GDBSTUB_XML removed Peter Maydell
2013-09-13 20:15 ` [Qemu-devel] [PATCH v2 0/4] avoid CONFIG_NO_* using rules.mak logic/string fns Paolo Bonzini
2013-09-27 3:02 ` Peter Maydell [this message]
2013-10-15 14:47 ` Peter Maydell
2013-10-15 14:55 ` Paolo Bonzini
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=CAFEAcA8fOJQxVFyvMjnd30274iRcLr+9dCa1QmKOTpc2XNXVbA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=akoskovacs@gmx.com \
--cc=anthony@codemonkey.ws \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).