From: Paolo Bonzini <pbonzini@redhat.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>, kvm@vger.kernel.org
Cc: frankja@linux.ibm.com, thuth@redhat.com, david@redhat.com,
drjones@redhat.com, jmattson@google.com,
sean.j.christopherson@intel.com
Subject: Re: [kvm-unit-tests PATCH v2 0/2] Fix some compilation issues on 32bit
Date: Tue, 28 Jul 2020 23:25:53 +0200 [thread overview]
Message-ID: <8d90b625-567d-e1b1-8533-996d654594f8@redhat.com> (raw)
In-Reply-To: <20200714130030.56037-1-imbrenda@linux.ibm.com>
On 14/07/20 15:00, Claudio Imbrenda wrote:
> Two small patches to fix compilation issues on 32bit:
>
> one for a typo in x86/cstart
>
> one for a thinko in lib/alloc_page
>
> notice that there is another patch for the lib/alloc_page issue floating
> around, this patch is an alternative to that one
>
> v1->v2
> * use the z modifier for size_t variables, instead of casting to long
>
> Claudio Imbrenda (2):
> x86/cstart: Fix compilation issue in 32 bit mode
> lib/alloc_page: Fix compilation issue on 32bit archs
>
> lib/alloc_page.c | 4 ++--
> x86/cstart.S | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
Queued these, thanks.
Paolo
prev parent reply other threads:[~2020-07-28 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 13:00 [kvm-unit-tests PATCH v2 0/2] Fix some compilation issues on 32bit Claudio Imbrenda
2020-07-14 13:00 ` [kvm-unit-tests PATCH v2 1/2] x86/cstart: Fix compilation issue in 32 bit mode Claudio Imbrenda
2020-07-15 14:29 ` Claudio Imbrenda
2020-07-14 13:00 ` [kvm-unit-tests PATCH v2 2/2] lib/alloc_page: Fix compilation issue on 32bit archs Claudio Imbrenda
2020-07-15 14:19 ` Thomas Huth
2020-07-16 7:11 ` Nadav Amit
2020-07-16 9:55 ` Claudio Imbrenda
2020-07-28 21:25 ` Paolo Bonzini [this message]
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=8d90b625-567d-e1b1-8533-996d654594f8@redhat.com \
--to=pbonzini@redhat.com \
--cc=david@redhat.com \
--cc=drjones@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=sean.j.christopherson@intel.com \
--cc=thuth@redhat.com \
/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.