History

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).

Florian Fainelli committed 7 years ago

Commit ffa91251 parent d0645cf1 file · +13 −0Browse files

Unified · Split

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

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t