On Fri, Aug 16, 2019 at 12:43:02PM -0700, mario.limoncie...@dell.com wrote:
> > We need to coordinate with Jens, don't think its a good idea if I'll
> > just randomly get stuff from linus' tree and send an rc pull request.
>
> The dependent commit is in Linus' tree now.
> 4eaefe8c621c6195c91044396
eam; Dominguez, Jared
> Subject: Re: [PATCH v2] nvme: Add quirk for LiteON CL1 devices running FW
> 2230
>
>
> [EXTERNAL EMAIL]
>
>
> >> Mario,
> >>
> >> Can you please respin a patch that applies cleanly on nvme-5.4?
> >
> > This fi
Mario,
Can you please respin a patch that applies cleanly on nvme-5.4?
This fixes a regression we introduced in 5.3, so it should go in
5.3-rc. For this to apply cleanly, though, we'll need to resync to Linus'
tree to get Rafael's PCIe ASPM check after he sends his linux-pm pull
request.
W
On Wed, Aug 14, 2019 at 01:14:50PM -0700, Sagi Grimberg wrote:
> Mario,
>
> Can you please respin a patch that applies cleanly on nvme-5.4?
This fixes a regression we introduced in 5.3, so it should go in
5.3-rc. For this to apply cleanly, though, we'll need to resync to Linus'
tree to get Rafael
; Dominguez, Jared
> Subject: Re: [PATCH v2] nvme: Add quirk for LiteON CL1 devices running FW
> 2230
>
>
> [EXTERNAL EMAIL]
>
> Mario,
>
> Can you please respin a patch that applies cleanly on nvme-5.4?
It looks like nvme-5.4 is missing the commit coming in from
Mario,
Can you please respin a patch that applies cleanly on nvme-5.4?
On Wed, Aug 14, 2019 at 01:08:24PM -0700, Mario Limonciello wrote:
> One of the components in LiteON CL1 device has limitations that
> can be encountered based upon boundary race conditions using the
> nvme bus specific suspend to idle flow.
>
> When this situation occurs the drive doesn't resume
7 matches
Mail list logo
