title: kernel.org stable Git : patch reachable from v5.11 but not v5.10-rcX
body: <p>I’ve run into a Git phenomenon the kernel.org stable repo that I can’t quite explain:</p>
  <p>There’s a specific patch I’m curious about (commit ID below) that isn’t reachable from where I’d expect it to be :</p>
  <pre><code>$ git describe 2224fc9efb2d6593fbfb57287e39ba4958b188ba
  v5.10-rc3-262-g2224fc9efb2d  #  ( upstreamed bewteen v5.10-rc3 and v5.10-rc4) 
  </code></pre>
  <p>But now, I see:</p>
  <pre><code>$ git log --no-merges --oneline v5.10-rc3..master | grep 2224fc9efb2d
  2224fc9efb2d KVM: x86: Expose AVX512_FP16 for supported CPUID
  $ git log --no-merges --oneline v5.10-rc3..v5.10-rc4 | grep 2224fc9efb2d 
  $ git log --no-merges --oneline v5.10-rc3..v5.10 | grep 2224fc9efb2d
  $ git log --no-merges --oneline v5.10-rc3..v5.11 | grep 2224fc9efb2d
  2224fc9efb2d KVM: x86: Expose AVX512_FP16 for supported CPUID
  </code></pre>
  <p>QUESTION: Why would that patch be <strong>unreachable</strong>* from the next RC tag, and unreachable from v5.10, but <em><strong>reachable</strong></em> from v5.11.X, and from master? What was likely done to hide the patch from v5.10-rc4 through v5.10.X ?</p>