qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: qemu-devel@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>,
	mst@redhat.com, Stefan Hajnoczi <stefanha@gmail.com>,
	Kevin O'Connor <kevin@koconnor.net>,
	Gerd Hoffmann <kraxel@redhat.com>,
	"Jordan Justen (Intel address)" <jordan.l.justen@intel.com>,
	Jeff Fan <jeff.fan@intel.com>
Subject: Re: [Qemu-devel] FW_CFG_NB_CPUS vs fwcfg file 'etc/boot-cpus'
Date: Fri, 11 Nov 2016 17:37:25 +0100	[thread overview]
Message-ID: <e33073e8-91a6-c919-03ad-bb763ef9086b@redhat.com> (raw)
In-Reply-To: <20161111153619.3ef19ccb@nial.brq.redhat.com>

On 11/11/16 15:36, Igor Mammedov wrote:

> I've already have a patch that makes upstream OVMF work for more
> than 64 CPUs and upto 288 (hopefully written in correct way).
> So expect me bothering you about boring stuff like rules where/how
> to post patches for edk2 and asking for review.

Great :)

Here's the list info:

https://lists.01.org/mailman/listinfo/edk2-devel

In particular, you have to be subscribed to be able to post. It's not
optimal, but that's how the list works for now.

Here's the official rules for contributing:

https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Development-Process

And here's my "somewhat more verbose" take on them:

https://github.com/tianocore/tianocore.github.io/wiki/Laszlo's-unkempt-git-guide-for-edk2-contributors-and-maintainers

Thanks,
Laszlo

      parent reply	other threads:[~2016-11-11 16:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 12:57 [Qemu-devel] FW_CFG_NB_CPUS vs fwcfg file 'etc/boot-cpus' Igor Mammedov
2016-11-11 14:02 ` Laszlo Ersek
2016-11-11 14:36   ` Igor Mammedov
2016-11-11 14:44     ` Kevin O'Connor
2016-11-11 15:05       ` Igor Mammedov
2016-11-11 16:37     ` Laszlo Ersek [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=e33073e8-91a6-c919-03ad-bb763ef9086b@redhat.com \
    --to=lersek@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=jeff.fan@intel.com \
    --cc=jordan.l.justen@intel.com \
    --cc=kevin@koconnor.net \
    --cc=kraxel@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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 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).