From mboxrd@z Thu Jan 1 00:00:00 1970 From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi) Date: Fri, 10 Aug 2018 16:13:41 +0100 Subject: [PATCH v3 0/2] PCI: imx: Initial imx7d pm support In-Reply-To: <52ee6376fa15d3a9a62bcfa5d87173e454ccc024.camel@nxp.com> References: <20180808111429.GC25150@e107981-ln.cambridge.arm.com> <20180808141938.GA30428@e107981-ln.cambridge.arm.com> <20180808152741.GA31808@e107981-ln.cambridge.arm.com> <52ee6376fa15d3a9a62bcfa5d87173e454ccc024.camel@nxp.com> Message-ID: <20180810151341.GA6863@e107981-ln.cambridge.arm.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Fri, Aug 10, 2018 at 11:11:55AM +0000, Leonard Crestez wrote: [...] > This needs further clarification: without the reset patch this will > hang on imx7 suspend/resume but this is the current behavior anyway. > > Both patches are required for imx7 pci suspend and including them out > of order shouldn't break unrelated functionality. > > So it should actually be fine to just include the pci changes now, > right? It is a bit late for v4.19 but before considering that, this series is actually a set of fixes, correct ? If that's the case I think Shawn can send them upstream for a v4.19-rc*, I can ACK them if that sounds reasonable. Patch (2) subject must make clear you are actually fixing a problem if we choose this course of action. Lorenzo