From: "Liu, Jing2" <jing2.liu@linux.intel.com>
To: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>, mst@redhat.com
Cc: anthony.xu@intel.com, lersek@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 2/2] hw/pci: add PCI resource reserve capability to legacy PCI bridge
Date: Thu, 6 Sep 2018 10:16:42 +0800 [thread overview]
Message-ID: <e6670c1e-6ecc-b8d2-5b26-c18f46ae1ee3@linux.intel.com> (raw)
In-Reply-To: <920bf34c-7328-9fc4-446d-20a04d00c75f@gmail.com>
Hi Marcle,
On 9/6/2018 12:36 AM, Marcel Apfelbaum wrote:
>
>
> On 09/05/2018 05:08 AM, Liu, Jing2 wrote:
>> Hi Marcel and Michael,
>>
>> Got no response so I would like to ask if I need do something more for
>> this serial? :)
>>
>
> Hi Jing,
>
> Maybe Michael is PTO, let's wait a few more days.
>
Thank you, I got it :)
BRs,
Jing
> Michael, I can send a pull request for this series if you are busy.
> Thanks,
> Marcel
>
>> Thanks,
>> Jing
>>
>> On 8/30/2018 10:58 AM, Liu, Jing2 wrote:
>>> Ping Michael :)
>>>
>>> Thanks,
>>> Jing
>>>
>>> On 8/25/2018 12:51 AM, Marcel Apfelbaum wrote:
>>>>>>>> On 08/21/2018 06:18 AM, Jing Liu wrote:
>>>>>>>>> Add hint to firmware (e.g. SeaBIOS) to reserve addtional
>>>>>>>>> BUS/IO/MEM/PREF resource for legacy pci-pci bridge. Add the
>>>>>>>>> resource reserve capability deleting in pci_bridge_dev_exitfn.
>>>>>>>>>
>>>>>>>>> Signed-off-by: Jing Liu <jing2.liu@linux.intel.com>
>>>>>>>>> ---
>>>>>>>>> hw/pci-bridge/pci_bridge_dev.c | 24 ++++++++++++++++++++++++
>>>>>>>>> 1 file changed, 24 insertions(+)
>>> [...]
>>>>>>>> Reviewed-by: Marcel Apfelbaum<marcel.apfelbaum@gmail.com>
>>>>>>>>
>>>>>>> Thanks for the quick reviewing and feedback.
>>>>>>> So could I ask what I should do now, update a new version
>>>>>>> with your rb or just waiting for pushing, or else?
>>>>>>>
>>>>>>
>>>>>> You just need to wait until Michael adds the series
>>>>>> to his next pull request. Nothing more to do.
>>>>>>
>>>>> OK, got it! Thanks!
>>>>
>>>> Please ping Michael if your code is not merged in a week or so.
>>>>
>>>>> BTW, do you have some suggestion on the seabios counterpart patches?
>>>>> https://patchew.org/Seabios/1534386737-8131-1-git-send-email-jing2.liu@linux.intel.com/
>>>>>
>>>>
>>>> I plan to have a look this weekend.
>>>>
>>>> Thanks,
>>>> Marcel
>>>
>
>
prev parent reply other threads:[~2018-09-06 2:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 3:18 [Qemu-devel] [PATCH v3 0/2] hw/pci: PCI resource reserve capability Jing Liu
2018-08-21 3:18 ` [Qemu-devel] [PATCH v3 1/2] hw/pci: factor PCI reserve resources to a separate structure Jing Liu
2018-08-21 9:55 ` Marcel Apfelbaum
2018-08-21 3:18 ` [Qemu-devel] [PATCH v3 2/2] hw/pci: add PCI resource reserve capability to legacy PCI bridge Jing Liu
2018-08-21 9:59 ` Marcel Apfelbaum
2018-08-22 1:53 ` Liu, Jing2
2018-08-22 6:58 ` Marcel Apfelbaum
2018-08-24 2:27 ` Liu, Jing2
2018-08-24 16:51 ` Marcel Apfelbaum
2018-08-27 3:33 ` Liu, Jing2
2018-08-30 2:58 ` Liu, Jing2
2018-09-05 2:08 ` Liu, Jing2
2018-09-05 16:36 ` Marcel Apfelbaum
2018-09-06 2:16 ` Liu, Jing2 [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=e6670c1e-6ecc-b8d2-5b26-c18f46ae1ee3@linux.intel.com \
--to=jing2.liu@linux.intel.com \
--cc=anthony.xu@intel.com \
--cc=lersek@redhat.com \
--cc=marcel.apfelbaum@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).