All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: Igor Mammedov <imammedo@redhat.com>,
	seabios@seabios.org, Laszlo Ersek <lersek@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [SeaBIOS PATCH 0/2] Allow non-contiguous APIC IDs (v3)
Date: Wed, 1 Aug 2012 10:47:35 +0300	[thread overview]
Message-ID: <20120801074735.GK11448@redhat.com> (raw)
In-Reply-To: <20120801011413.GE22937@morn.localdomain>

On Tue, Jul 31, 2012 at 09:14:13PM -0400, Kevin O'Connor wrote:
> On Wed, Jul 25, 2012 at 03:45:28PM -0300, Eduardo Habkost wrote:
> > Changes v2 -> v3:
> >  - Report I/O APIC ID = 0 on MP-table, too
> > 
> > Changes v1 -> v2:
> >  - Patch 1/2: cosmetic whitespace change
> >  - Patch 2/2: use size suffixes on asm instructions on smp.c
> >  - New patch descriptions
> > 
> > Eduardo Habkost (2):
> >   report real I/O APIC ID (0) on MADT and MP-table (v3)
> >   allow CPUs to have non-contiguous Local APIC IDs (v2)
> 
> The series looks okay to me.  However, I think Gleb and Avi had some
> comments - has that been resolved now?
> 
No, but the comment is very minor and can be resolved by follow up
patch if ever.

--
			Gleb.

  reply	other threads:[~2012-08-01  7:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-25 18:45 [Qemu-devel] [SeaBIOS PATCH 0/2] Allow non-contiguous APIC IDs (v3) Eduardo Habkost
2012-07-25 18:45 ` [Qemu-devel] [SeaBIOS PATCH 1/2] report real I/O APIC ID (0) on MADT and MP-table (v3) Eduardo Habkost
2012-07-25 18:45 ` [Qemu-devel] [SeaBIOS PATCH 2/2] allow CPUs to have non-contiguous Local APIC IDs (v2) Eduardo Habkost
2012-07-27 13:42   ` Laszlo Ersek
2012-07-27 13:43     ` Laszlo Ersek
2012-08-01  1:14 ` [Qemu-devel] [SeaBIOS PATCH 0/2] Allow non-contiguous APIC IDs (v3) Kevin O'Connor
2012-08-01  7:47   ` Gleb Natapov [this message]
2012-08-02  0:49     ` Kevin O'Connor

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=20120801074735.GK11448@redhat.com \
    --to=gleb@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=kevin@koconnor.net \
    --cc=lersek@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.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 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.