From: "Wei, Jiangang" <weijg.fnst@cn.fujitsu.com>
To: "mst@redhat.com" <mst@redhat.com>
Cc: "marcel@redhat.com" <marcel@redhat.com>,
"armbru@redhat.com" <armbru@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] Convert pxb initfn to Error
Date: Fri, 8 Apr 2016 07:58:03 +0000 [thread overview]
Message-ID: <1460102255.10782.17.camel@localhost> (raw)
In-Reply-To: <20160407195456-mutt-send-email-mst@redhat.com>
On Thu, 2016-04-07 at 19:55 +0300, Michael S. Tsirkin wrote:
> On Thu, Apr 07, 2016 at 07:44:17PM +0300, Michael S. Tsirkin wrote:
> > On Thu, Apr 07, 2016 at 06:39:10PM +0200, Markus Armbruster wrote:
> > > Marcel Apfelbaum <marcel@redhat.com> writes:
> > >
> > > > On 03/23/2016 01:56 PM, Markus Armbruster wrote:
> > > >> Wei Jiangang <weijg.fnst@cn.fujitsu.com> writes:
> > > >>
> > > >>> v1 -> v2:
> > > >>>
> > > >>> - Extract a separate bugfix patch
> > > >>> - Squash v1 patches 1-3 together
> > > >>> - Drop the period and exclamation mark
> > > >>> - Modify commit message
> > > >>>
> > > >>> v1: cover-letter
> > > >>>
> > > >>> The original patch named '[PATCH v3] PXB: convert to realize()'
> > > >>> was raised by Cao jin <caoj.fnst@cn.fujitsu.com>,
> > > >>> and reviewed by Marcel Apfelbaum <marcel@redhat.com>.
> > > >>>
> > > >>> It conflicts with 02b0743 that had been merged,
> > > >>> so resend a newer version, including the following,
> > > >>
> > > >> Series
> > > >> Reviewed-by: Markus Armbruster <armbru@redhat.com>
> > > >>
> > > >
> > > > Thanks Markus, will you take it in your tree, or Michael ?
> > >
> > > As error reporting maintainer, I cover error reporting infrastructure.
> > > I also take non-infrastructure error reporting patches that cross
> > > subsystems when no affected maintainer objects, single-subsystem patches
> > > when the maintainer asks me to, and patches to unmaintained code.
> > >
> > > I encourage you to take this series through the PCI tree. But if you
> > > want me to take it through my tree instead, let me know.
> >
> > I applied this, thanks!
>
> In fact, I applied patch 1/2. 2/2 fails build and is not a bugfix.
> I think it's best to defer it to after 2.6.
> Pls repost it then.
Hi,
I have fixed the compile error.
In fact, I missed including the qapi/error.h.
May I trouble you to check and apply v3 again ?
Thanks in advance.
wei
>
prev parent reply other threads:[~2016-04-08 7:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 7:26 [Qemu-devel] [PATCH v2 0/2] Convert pxb initfn to Error Wei Jiangang
2016-03-23 7:26 ` [Qemu-devel] [PATCH v2 1/2] hw/pci-bridge: Add missing unref in case register-bus fails Wei Jiangang
2016-03-27 15:13 ` Marcel Apfelbaum
2016-03-23 7:26 ` [Qemu-devel] [PATCH v2 2/2] hw/pci-bridge: Convert pxb initialization functions to Error Wei Jiangang
2016-03-23 7:52 ` Cao jin
2016-03-23 11:56 ` Markus Armbruster
2016-03-27 15:21 ` Marcel Apfelbaum
2016-03-23 11:56 ` [Qemu-devel] [PATCH v2 0/2] Convert pxb initfn " Markus Armbruster
2016-03-27 15:22 ` Marcel Apfelbaum
2016-04-07 16:39 ` Markus Armbruster
2016-04-07 16:44 ` Michael S. Tsirkin
2016-04-07 16:55 ` Michael S. Tsirkin
2016-04-08 7:55 ` [Qemu-devel] [PATCH v3 2/2] hw/pci-bridge: Convert pxb initialization functions " Wei Jiangang
2016-04-08 9:35 ` Michael S. Tsirkin
2016-04-08 7:58 ` Wei, Jiangang [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=1460102255.10782.17.camel@localhost \
--to=weijg.fnst@cn.fujitsu.com \
--cc=armbru@redhat.com \
--cc=marcel@redhat.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).