From: Zhenzhong Duan <zhenzhong.duan@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-Devel <xen-devel@lists.xen.org>,
manoj.gopalasetty@hpe.com, david.westwood@hpe.com,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Srinivas REDDY Eeda <srinivas.eeda@oracle.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH RESEND v3 1/2] x86/mmcfg: Rename pt_pci_init() and call it in acpi_mmcfg_init()
Date: Mon, 27 Aug 2018 16:57:14 +0800 [thread overview]
Message-ID: <d369a5e2-f8ff-d0f4-b8e5-3041c35b0860@oracle.com> (raw)
In-Reply-To: <5B83B34B02000078001E2048@prv1-mh.provo.novell.com>
在 2018/8/27 16:16, Jan Beulich 写道:
>>>> On 22.08.18 at 11:16, <zhenzhong.duan@oracle.com> wrote:
>> Given what pt_pci_init() actually does, rename it properly and move its
>> declaration to pci.h, move the only call in acpi_mmcfg_init().
>>
>> No functional change.
>>
>> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@oracle.com>
>> Tested-by: Gopalasetty, Manoj <manoj.gopalasetty@hpe.com>
>> Acked-by: Jan Beulich <jbeulich@suse.com>
>
> Please avoid needless re-sending of patches that have already
> gone in. Roger's remark regarding the questionable solitary v3
> 2/2 was correct, just that you should have dropped the 2/2
> instead of re-sending an already applied patch.
Ok.
To avoid endless resending, I'll follow that way next time.
Thanks
Zhenzhong
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2018-08-27 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 9:16 [PATCH RESEND v3 1/2] x86/mmcfg: Rename pt_pci_init() and call it in acpi_mmcfg_init() Zhenzhong Duan
2018-08-27 8:16 ` Jan Beulich
2018-08-27 8:57 ` Zhenzhong Duan [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=d369a5e2-f8ff-d0f4-b8e5-3041c35b0860@oracle.com \
--to=zhenzhong.duan@oracle.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.westwood@hpe.com \
--cc=manoj.gopalasetty@hpe.com \
--cc=roger.pau@citrix.com \
--cc=srinivas.eeda@oracle.com \
--cc=xen-devel@lists.xen.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).