qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bret Ketchum <bcketchum@gmail.com>
To: qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] Qemu IPMI support
Date: Tue, 5 Nov 2013 10:43:27 -0600	[thread overview]
Message-ID: <CAGm6yaQ7kxceBUPjWCjsRTvAyWKxaisM2A8_PdNNGg1O-bwx_g@mail.gmail.com> (raw)
In-Reply-To: <20131105135305.GA3696@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]

   Will do, thanks.


On Tue, Nov 5, 2013 at 7:53 AM, Michael S. Tsirkin <mst@redhat.com> wrote:

> On Tue, Nov 05, 2013 at 07:27:42AM -0600, Bret Ketchum wrote:
> > Gentlemen,
> >
> >     Hope this email finds you well and hope you can point me in the right
> > direction. I've a project which requires a VM to see a BMC at an IO Port
> on an
> > ISA bus. I've adapted (rather in the process of) the patches described
> here:
> >
> > http://lists.gnu.org/archive/html/qemu-devel/2013-05/msg04335.html
> >
> >     To 1.6.1 but am wondering about the process where a patch on
> qemu-devel
> > finds its way into a release. I'd like to see Corey's patch become
> reality for
> > obvious reasons. How may I facilitate this patch becoming a part of a
> future
> > release?
> >
> >     Any insight is appreciated and thanks in advance.
> >
> >     Bret
> >
> >
>
> I think it's a good idea to rebase this on top of latest bits.
>
> In particular, there's no need to add FW CFG interfaces
> anymore, now that we generate the ACPI tables in QEMU.
>
> Pls Cc me on the series when you post them,
> I'll try to help review.
>
> --
> MST
>

[-- Attachment #2: Type: text/html, Size: 1809 bytes --]

       reply	other threads:[~2013-11-05 16:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGm6yaQdByfFu=8qv4+tt01jE=uDupFzDcXUBghFA0YJaRn1cQ@mail.gmail.com>
     [not found] ` <20131105135305.GA3696@redhat.com>
2013-11-05 16:43   ` Bret Ketchum [this message]
     [not found] <9C46C997A77C834C81ACBF2B3F67C31705657234BF@MX43A.corp.emc.com>
     [not found] ` <551ED8C5.7020003@acm.org>
     [not found]   ` <9C46C997A77C834C81ACBF2B3F67C31705657237D7@MX43A.corp.emc.com>
2015-04-05  2:02     ` [Qemu-devel] QEMU IPMI support Corey Minyard
2015-04-07 12:24       ` Longever, Joseph
2015-04-07 12:43         ` Corey Minyard
2015-04-07 12:51           ` Longever, Joseph
2015-04-07 15:05           ` Longever, Joseph
2015-04-07 12:31       ` Corey Minyard

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=CAGm6yaQ7kxceBUPjWCjsRTvAyWKxaisM2A8_PdNNGg1O-bwx_g@mail.gmail.com \
    --to=bcketchum@gmail.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.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).