From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from userp2130.oracle.com ([156.151.31.86]:57664 "EHLO userp2130.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752866AbeCUQlT (ORCPT ); Wed, 21 Mar 2018 12:41:19 -0400 From: Rao Shoaib Subject: Few questions about submitting patches To: netdev , David Miller , Eric Dumazet Message-ID: Date: Wed, 21 Mar 2018 09:41:13 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: netdev-owner@vger.kernel.org List-ID: I am new to Linux. I would like to understand the rules and etiquettes of engaging with the community. I have read the materials that I could find. As I work with Linux I come across situations for which I can not seem to find any answers. Hopefully folks on the list can answer them. * Submitting an RFC Patch As I understand, an RFC patch is submitted to solicit comments and is not for inclusion. Is it sufficient for an RFC patch to have the correct coding style and compile, or does it need more? For example, If the patch consists of a series of patches, does each patch have to compile independently etc etc. * #ifdef FOO In a regular patch consisting of a series of patches, can the above #ifdef be used in a patch before the patch that allows the selection of FOO. That patch is part of the series but comes later. Regards, Shoaib