From: Avi Kivity <avi@redhat.com>
To: Borislav Petkov <bp@alien8.de>,
Marcelo Tosatti <mtosatti@redhat.com>,
Ingo Molnar <mingo@elte.hu>,
kvm@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
Subject: Re: [PATCH] kvm: Fix build warnings
Date: Tue, 07 Jun 2011 10:58:08 +0300 [thread overview]
Message-ID: <4DEDDA10.1080603@redhat.com> (raw)
In-Reply-To: <20110607072813.GC21263@liondog.tnic>
On 06/07/2011 10:28 AM, Borislav Petkov wrote:
> So, any progress on this front? Warning is still there in -rc2.
>
Thanks for the reminder, applied and queued.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Borislav Petkov <bp@alien8.de>,
Marcelo Tosatti <mtosatti@redhat.com>,
Ingo Molnar <mingo@elte.hu>,
kvm@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Takuya Yoshikawa <yoshik
Subject: Re: [PATCH] kvm: Fix build warnings
Date: Tue, 07 Jun 2011 10:58:08 +0300 [thread overview]
Message-ID: <4DEDDA10.1080603@redhat.com> (raw)
In-Reply-To: <20110607072813.GC21263@liondog.tnic>
On 06/07/2011 10:28 AM, Borislav Petkov wrote:
> So, any progress on this front? Warning is still there in -rc2.
>
Thanks for the reminder, applied and queued.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2011-06-07 7:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 9:46 KVM build warnings Borislav Petkov
2011-05-30 10:14 ` Takuya Yoshikawa
2011-05-30 12:46 ` Borislav Petkov
2011-05-30 20:11 ` [PATCH] kvm: Fix " Borislav Petkov
2011-05-31 7:38 ` Ingo Molnar
2011-05-31 8:19 ` Takuya Yoshikawa
2011-05-31 8:20 ` Avi Kivity
2011-05-31 9:02 ` Borislav Petkov
2011-05-31 10:26 ` Ingo Molnar
2011-06-07 7:28 ` Borislav Petkov
2011-06-07 7:58 ` Avi Kivity [this message]
2011-06-07 7:58 ` Avi Kivity
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=4DEDDA10.1080603@redhat.com \
--to=avi@redhat.com \
--cc=bp@alien8.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.com \
--cc=yoshikawa.takuya@oss.ntt.co.jp \
/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.