On Thu, Mar 21, 2024 at 07:57:28AM +0000, Liuye wrote: > > > The stack trace below shows an example of the problem. In this case > > the master cpu is not running from NMI but it has parked the slave > > CPUs using an NMI and the parked CPUs is holding spinlocks needed by > > schedule_work(). > > Add description information > > > Signed-off-by: LiuYe <liu.yeC@xxxxxxx> > > Co-authored-by: Daniel Thompson <daniel.thompson@xxxxxxxxxx> > > Signed-off-by: Daniel Thompson <daniel.thompson@xxxxxxxxxx> > > Add > Co-authored-by: Daniel Thompson <daniel.thompson@xxxxxxxxxx> > Signed-off-by: Daniel Thompson <daniel.thompson@xxxxxxxxxx> I assume this reply is summarizing what changed between the previous version and v3? The best way to add the changelog requested by Greg's bot is to send a corrected v4 version. If you follow the example in https://docs.kernel.org/process/submitting-patches.html#the-canonical-patch-format then you'll see that what is expected. You can use git-notes to handle this. If you add a note containing something like the following: ~~~ Changes in v4: * Provide these changelogs. Changes in v3: * <please describe changes> Changes in v2: * <please describe changes> ~~~ Once you have the note than git-format-patch --notes will automatically included the changelog with the patch. Daniel. PS I know that v2 was circulated with an incorrect subject line but I think it is probably OK to call it v2 anyway... it makes the changelog clearer!
