All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-trivial <qemu-trivial@nongnu.org>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Michael Tokarev <mjt@tls.msk.ru>, Alexander Graf <agraf@suse.de>,
	qemu-devel <qemu-devel@nongnu.org>,
	liguang <lig.fnst@cn.fujitsu.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-trivial] [PATCH] cputlb: remove dead function tlb_update_dirty
Date: Wed, 04 Sep 2013 12:59:25 +0200	[thread overview]
Message-ID: <5227128D.705@redhat.com> (raw)
In-Reply-To: <52261431.5050705@suse.de>

Il 03/09/2013 18:54, Andreas Färber ha scritto:
> Also, I am seeing Paolo pull in huge memory changes but now pinging the
> breakage fixes rather than assembling a pull to fix the fallout. ;)

Well, I didn't put myself as memory maintainer for a reason. :)  But it
looks like a pull request is the best thing to do, so I'll find some
time this week to make one.

Paolo


WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-trivial <qemu-trivial@nongnu.org>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Michael Tokarev <mjt@tls.msk.ru>, Alexander Graf <agraf@suse.de>,
	qemu-devel <qemu-devel@nongnu.org>,
	liguang <lig.fnst@cn.fujitsu.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] cputlb: remove dead function tlb_update_dirty
Date: Wed, 04 Sep 2013 12:59:25 +0200	[thread overview]
Message-ID: <5227128D.705@redhat.com> (raw)
In-Reply-To: <52261431.5050705@suse.de>

Il 03/09/2013 18:54, Andreas Färber ha scritto:
> Also, I am seeing Paolo pull in huge memory changes but now pinging the
> breakage fixes rather than assembling a pull to fix the fallout. ;)

Well, I didn't put myself as memory maintainer for a reason. :)  But it
looks like a pull request is the best thing to do, so I'll find some
time this week to make one.

Paolo

  parent reply	other threads:[~2013-09-04 10:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03  7:05 [Qemu-devel] [PATCH] cputlb: remove dead function tlb_update_dirty liguang
2013-09-03  7:22 ` [Qemu-trivial] " Paolo Bonzini
2013-09-03  7:22   ` [Qemu-devel] " Paolo Bonzini
2013-09-03  8:35   ` [Qemu-trivial] " Andreas Färber
2013-09-03  8:35     ` [Qemu-devel] " Andreas Färber
2013-09-03  8:41     ` [Qemu-trivial] " Paolo Bonzini
2013-09-03  8:41       ` [Qemu-devel] " Paolo Bonzini
2013-09-03  8:48     ` [Qemu-trivial] " Peter Maydell
2013-09-03  8:48       ` [Qemu-devel] " Peter Maydell
2013-09-03 11:17     ` [Qemu-trivial] " Michael Tokarev
2013-09-03 11:17       ` [Qemu-devel] " Michael Tokarev
2013-09-03 16:54       ` Andreas Färber
2013-09-03 16:54         ` [Qemu-devel] " Andreas Färber
2013-09-04  1:36         ` Li Guang
2013-09-04  1:36           ` [Qemu-devel] " Li Guang
2013-09-04 10:59         ` Paolo Bonzini [this message]
2013-09-04 10:59           ` 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=5227128D.705@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=jan.kiszka@siemens.com \
    --cc=lig.fnst@cn.fujitsu.com \
    --cc=mjt@tls.msk.ru \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=rth@twiddle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.