linux-kernel - Re: [PATCH 2/3] Refactor msi/msix restore code Part2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130802120101.GE24540@konrad-lan.dumpdata.com>
Date:	Fri, 2 Aug 2013 08:01:02 -0400
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	Zhenzhong Duan <zhenzhong.duan@...cle.com>
Cc:	Bjorn Helgaas <bhelgaas@...gle.com>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	xen-devel <xen-devel@...ts.xen.org>,
	Feng Jin <joe.jin@...cle.com>,
	Sucheta Chakraborty <sucheta.chakraborty@...gic.com>
Subject: Re: [PATCH 2/3] Refactor msi/msix restore code Part2

> >>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?

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/