Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

Documentation: networking: Update netdev-FAQ regarding patches

Provide an explanation of what is expected with respect to sending new
versions of specific patches within a patch series, as well as what
happens if an earlier patch series accidentally gets merged).

Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

authored by

Florian Fainelli and committed by
David S. Miller
ffa91253 d0645cfd

+13
+13
Documentation/networking/netdev-FAQ.rst
··· 131 131 version that should be applied. If there is any doubt, the maintainer 132 132 will reply and ask what should be done. 133 133 134 + Q: I made changes to only a few patches in a patch series should I resend only those changed? 135 + -------------------------------------------------------------------------------------------- 136 + A: No, please resend the entire patch series and make sure you do number your 137 + patches such that it is clear this is the latest and greatest set of patches 138 + that can be applied. 139 + 140 + Q: I submitted multiple versions of a patch series and it looks like a version other than the last one has been accepted, what should I do? 141 + ------------------------------------------------------------------------------------------------------------------------------------------- 142 + A: There is no revert possible, once it is pushed out, it stays like that. 143 + Please send incremental versions on top of what has been merged in order to fix 144 + the patches the way they would look like if your latest patch series was to be 145 + merged. 146 + 134 147 Q: How can I tell what patches are queued up for backporting to the various stable releases? 135 148 -------------------------------------------------------------------------------------------- 136 149 A: Normally Greg Kroah-Hartman collects stable commits himself, but for