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
| ||
|
Message-ID: <5A42F925.5090806@rock-chips.com> Date: Wed, 27 Dec 2017 09:36:37 +0800 From: JeffyChen <jeffy.chen@...k-chips.com> To: "Rafael J. Wysocki" <rjw@...ysocki.net>, Rob Herring <robh@...nel.org> CC: linux-kernel@...r.kernel.org, bhelgaas@...gle.com, linux-pm@...r.kernel.org, tony@...mide.com, shawn.lin@...k-chips.com, briannorris@...omium.org, dianders@...omium.org, devicetree@...r.kernel.org, linux-pci@...r.kernel.org, Mark Rutland <mark.rutland@....com> Subject: Re: [RFC PATCH v12 1/5] dt-bindings: PCI: Add definition of PCIe WAKE# irq and PCI irq Hi Rafael and Rob, Thanks for your reply. On 12/27/2017 08:43 AM, Rafael J. Wysocki wrote: > On Wednesday, December 27, 2017 12:35:52 AM CET Rob Herring wrote: >> >On Tue, Dec 26, 2017 at 10:36:42AM +0800, Jeffy Chen wrote: >>> > >We are going to handle PCIe WAKE# pin for PCI devices in the pci core, >>> > >so add definitions of the optional PCIe WAKE# pin for PCI devices. >>> > > >>> > >Also add an definition of the optional PCI interrupt pin for PCI >>> > >devices to distinguish it from the PCIe WAKE# pin. >> > >> >By v13 you should drop "RFC". RFC implies not ready for merging. > Which very much still is the case AFAICS. > maybe i should split this series, and send dt-binding patch and the pci irq parsing patch along without RFC ? > Thanks, > Rafael > > > >
Powered by blists - more mailing lists