linux-kernel - Re: [PATCH v3 04/12] PCI: Destroy pci dev only once

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] [day] [month] [year] [list]

Date:	Wed, 04 Dec 2013 21:03:05 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Bjorn Helgaas <bhelgaas@...gle.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	Gu Zheng <guz.fnst@...fujitsu.com>,
	Guo Chao <yan@...ux.vnet.ibm.com>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 04/12] PCI: Destroy pci dev only once

On Tuesday, December 03, 2013 06:19:28 PM Yinghai Lu wrote:
> On Sat, Nov 30, 2013 at 5:05 PM, Rafael J. Wysocki <rjw@...ysocki.net> wrote:
> > On Saturday, November 30, 2013 02:40:30 PM Yinghai Lu wrote:
> >
> > And this is not enough as I said, can you please stop ignoring me openly?
> >
> > You've already commented the last patch I posted, so why don't we finish
> > that discussion first?
> 
> No, i did not mean that.
> 
> I resent the whole patchset as I added pci_clip_resource() and that
> will need to revise several critial patches, and Bjorn does not like
> to have patches to be attached format.

I see.

> Also in the patcheset head mail, i did state that you have another
> solution using
> lock.
> 
> And your patch is quite big, please give me some time to digest it.

Yes, it is, please take your time. :-)

Thanks,
Rafael

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