From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"mm-commits@vger.kernel.org" <mm-commits@vger.kernel.org>,
"alan@linux.intel.com" <alan@linux.intel.com>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
"dcb314@hotmail.com" <dcb314@hotmail.com>,
"mtosatti@redhat.com" <mtosatti@redhat.com>,
"paulus@samba.org" <paulus@samba.org>,
KVM list <kvm@vger.kernel.org>
Subject: Re: + ppc-e500_tlb-memset-clears-nothing.patch added to -mm tree
Date: Wed, 25 Jul 2012 12:20:41 +0300 [thread overview]
Message-ID: <500FBA69.9070402@redhat.com> (raw)
In-Reply-To: <A8F92187-840B-4572-8952-7CD53227C362@suse.de>
On 07/25/2012 12:00 PM, Alexander Graf wrote:
>
> On 25.07.2012, at 10:32, Avi Kivity <avi@redhat.com> wrote:
>
>> On 07/25/2012 12:00 AM, akpm@linux-foundation.org wrote:
>>> The patch titled
>>> Subject: ppc: e500_tlb memset clears nothing
>>> has been added to the -mm tree. Its filename is
>>> ppc-e500_tlb-memset-clears-nothing.patch
>>>
>>
>> The kvm tree is maintained. Alex, please pick up this patch; I guess
>> it's 3.6 material.
>
> Yeah, not sure what's going on here. Alan sent me the patch a while back in a private mail, so I asked him to resend it to the ML, so it's available for review. Next thing that happens is this mail a few weeks later.
>
> Either way, will bypass the normal process this time and pull it in my queue. It is certainly 3.6 material.
I wonder how many such bugs a memzero()/bzero() will prevent.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-07-25 9:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120724210054.4164420004E@hpza10.eem.corp.google.com>
2012-07-25 8:32 ` + ppc-e500_tlb-memset-clears-nothing.patch added to -mm tree Avi Kivity
2012-07-25 9:00 ` Alexander Graf
2012-07-25 9:20 ` Avi Kivity [this message]
2012-07-25 10:12 ` Alan Cox
2012-07-25 10:20 ` Avi Kivity
2012-07-25 10:10 ` Alan Cox
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=500FBA69.9070402@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=benh@kernel.crashing.org \
--cc=dcb314@hotmail.com \
--cc=kvm@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=paulus@samba.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).