From: Zhenzhong Duan <zhenzhong.duan@oracle.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
xen-devel <xen-devel@lists.xen.org>,
Feng Jin <joe.jin@oracle.com>,
Sucheta Chakraborty <sucheta.chakraborty@qlogic.com>
Subject: Re: [PATCH 2/3] Refactor msi/msix restore code Part2
Date: Mon, 05 Aug 2013 15:19:07 +0800 [thread overview]
Message-ID: <51FF51EB.9070907@oracle.com> (raw)
In-Reply-To: <20130802120101.GE24540@konrad-lan.dumpdata.com>
On 2013-08-02 20:01, Konrad Rzeszutek Wilk wrote:
>>>> Konrad, are you OK with this patch now?
>>> Yes, I wanted to make sure that the existing behavior under baremetal
>>> was not altered.
>>>
>>> And Duan had confirmed it was not - thought to be on a safe side it
>>> would be good to confirm this via testing just in case.
>> I had ever let our customer test on baremetal and it passed.
> Are they OK with being credited for this in the patch? Meaning are they
> OK with Reported-by-and-Tested-by: flag?
sucheta.chakraborty from Qlogic also reproduced the same and I got his
confirm patch worked.
Already add him in tested-by.
zduan
>
> Either way, I think the only remaining issue is to expand the git commit
> a bit to include the discussion about the flow of the pci_read/pci_write
> and point out that the logic remains the same.
>
>
>> zduan
next prev parent reply other threads:[~2013-08-05 7:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 3:08 [PATCH 2/3] Refactor msi/msix restore code Part2 Zhenzhong Duan
2013-07-24 13:46 ` Konrad Rzeszutek Wilk
2013-07-24 13:46 ` Konrad Rzeszutek Wilk
2013-07-25 6:52 ` Zhenzhong Duan
2013-07-25 12:25 ` Konrad Rzeszutek Wilk
2013-07-25 12:25 ` Konrad Rzeszutek Wilk
2013-07-26 3:01 ` Zhenzhong Duan
2013-07-26 3:01 ` Zhenzhong Duan
2013-07-25 6:52 ` Zhenzhong Duan
2013-07-31 22:41 ` Bjorn Helgaas
2013-08-01 15:16 ` Konrad Rzeszutek Wilk
2013-08-02 9:16 ` Zhenzhong Duan
2013-08-02 9:16 ` Zhenzhong Duan
2013-08-02 12:01 ` Konrad Rzeszutek Wilk
2013-08-05 7:19 ` Zhenzhong Duan
2013-08-05 7:19 ` Zhenzhong Duan [this message]
2013-08-02 12:01 ` Konrad Rzeszutek Wilk
2013-08-01 15:16 ` Konrad Rzeszutek Wilk
2013-07-31 22:41 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2013-07-24 3:08 Zhenzhong Duan
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=51FF51EB.9070907@oracle.com \
--to=zhenzhong.duan@oracle.com \
--cc=bhelgaas@google.com \
--cc=joe.jin@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sucheta.chakraborty@qlogic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.