On Wed, 2019-07-24 at 12:11 +0100, Lorenzo Pieralisi wrote: > On Tue, Jul 23, 2019 at 03:12:51PM +0000, Derrick, Jonathan wrote: > > [...] > > > > > Besides the stable issue, can we get this into 5.3? > > > > > > Usually we send fixes at -rc for patches that were merged in the > > > previous merge window; this fix is not one of those so I think > > > we will send it for v5.4 unless it is very urgent. > > > > > > We should still update stable info in the log appropriately > > > before queuing it. > > > > > > Thanks, > > > Lorenzo > > > > Sure. Had assumed it would be queued for 5.3 as it was submitted in 5.2 > > I will resubmit during 5.4 merge window and deal with stables later. > > It should not be that complicated to add stable tags (possibly > with commit dependencies on stable kernels where the patch > does not apply and require additional patches to be pulled), > there is plenty of time to sort this out. > > Apologies for not picking it up for v5.3 - I should have asked > you to just update the stable tag so that we could merge it. > > Lorenzo No problem. I have another fix I need to include so I will do that during 5.4 merge window
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
