On Thu, Jun 10, 2021 at 1:25 AM Greg KH gregkh@linuxfoundation.org wrote:
On Wed, Jun 09, 2021 at 08:25:47PM -0400, Pascal Giard wrote:
I apologize for failing to follow the procedure. I had already read these guidelines, and I actually thought I was following Option 1 :-/
Is this commit already in Linus's tree? If so then we just need a git commit id and we can queue it up.
No, it isn't yet. My patch has not been reviewed yet.
I thought that I had to get my patch merged into next first (patch against dtor's git) and that by adding stable@ as CC, it would automatically get considered for inclusion into stable once merged into Linus' tree. Based on your email, I got that wrong...
It will, but you need to add that to the signed-off-by: area, as the document says.
Oh dear, that's the bit I missed.
At this point I assume that I should not resubmit a patch (to avoid unnecessary noise) and patiently wait for a review, e.g., by Jiri, for it to be included in next.
From there, I'll try to do the right thing (CC stable in the
signed-off area) shall a new version be necessary or follow option 2 with the commit id when it gets merged to Linus' tree.
Once again, my apologies for failing to follow the procedure and thank you for your patience.
-Pascal