mirror of
				https://github.com/torvalds/linux.git
				synced 2025-11-04 02:30:34 +02:00 
			
		
		
		
	docs: netdev: add a note on selftest posting
We haven't had much discussion on the list about this, but a handful of people have been confused about rules on posting selftests for fixes, lately. I tend to post fixes with their respective selftests in the same series. There are tradeoffs around size of the net tree and conflicts but so far it hasn't been a major issue. Signed-off-by: Jakub Kicinski <kuba@kernel.org> Acked-by: Cong Wang <xiyou.wangcong@gmail.com> Link: https://patch.msgid.link/20250306180533.1864075-1-kuba@kernel.org Signed-off-by: Paolo Abeni <pabeni@redhat.com>
This commit is contained in:
		
							parent
							
								
									6d99faf254
								
							
						
					
					
						commit
						0ea09cbf83
					
				
					 1 changed files with 8 additions and 0 deletions
				
			
		| 
						 | 
					@ -311,6 +311,14 @@ to the mailing list, e.g.::
 | 
				
			||||||
Posting as one thread is discouraged because it confuses patchwork
 | 
					Posting as one thread is discouraged because it confuses patchwork
 | 
				
			||||||
(as of patchwork 2.2.2).
 | 
					(as of patchwork 2.2.2).
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					Co-posting selftests
 | 
				
			||||||
 | 
					--------------------
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					Selftests should be part of the same series as the code changes.
 | 
				
			||||||
 | 
					Specifically for fixes both code change and related test should go into
 | 
				
			||||||
 | 
					the same tree (the tests may lack a Fixes tag, which is expected).
 | 
				
			||||||
 | 
					Mixing code changes and test changes in a single commit is discouraged.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
Preparing changes
 | 
					Preparing changes
 | 
				
			||||||
-----------------
 | 
					-----------------
 | 
				
			||||||
 | 
					
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
		Loading…
	
		Reference in a new issue