Hello, I was going through kernel source and found out that I can work on staging area for fixes.
I have generated a patch for coding style fixes. I have few questions about how do submit my patch and to whom. 1) Is it ok if I send it directly to Greg Kroah-Hartman <[email protected]>, who seems to be signing off all the patches in that directory as per git log. 2) What is the standard procedure to submit my patch after I have verified it. Whom do I send it? How do I get it review? How to get it merged in mainline? Also, I am attaching my patch here. Any suggestions on patch and answer to my queries will be great help. Thanks, Sunil.
From d09048ffe41531d691df9d90fe25e34ffc11c8f8 Mon Sep 17 00:00:00 2001 From: Sunil Shahu <[email protected]> Date: Sun, 2 Nov 2014 19:37:15 +0530 Subject: [PATCH] staging: bcm: vendorspecificextn: Fix coding style This fixes the coding style warnings of line over 80 characters. Signed-off-by: Sunil Shahu <[email protected]> --- drivers/staging/bcm/vendorspecificextn.c | 23 ++++++++++++++--------- 1 file changed, 14 insertions(+), 9 deletions(-) diff --git a/drivers/staging/bcm/vendorspecificextn.c b/drivers/staging/bcm/vendorspecificextn.c index d38a06f..797d21d 100644 --- a/drivers/staging/bcm/vendorspecificextn.c +++ b/drivers/staging/bcm/vendorspecificextn.c @@ -11,7 +11,8 @@ * STATUS_SUCCESS/STATUS_FAILURE * */ -INT vendorextnGetSectionInfo(PVOID pContext, struct bcm_flash2x_vendor_info *pVendorInfo) +INT vendorextnGetSectionInfo(PVOID pContext, + struct bcm_flash2x_vendor_info *pVendorInfo) { return STATUS_FAILURE; } @@ -61,8 +62,9 @@ INT vendorextnExit(struct bcm_mini_adapter *Adapter) * arg -input parameter sent by vendor * * Returns: - * CONTINUE_COMMON_PATH in case it is not meant to be processed by vendor ioctls - * STATUS_SUCCESS/STATUS_FAILURE as per the IOCTL return value + * CONTINUE_COMMON_PATH in case it is not meant to be processed by + * vendor ioctls STATUS_SUCCESS/STATUS_FAILURE as per the IOCTL + * return value */ INT vendorextnIoctl(struct bcm_mini_adapter *Adapter, UINT cmd, ULONG arg) @@ -88,8 +90,9 @@ INT vendorextnIoctl(struct bcm_mini_adapter *Adapter, UINT cmd, ULONG arg) * STATUS_SUCCESS/STATUS_FAILURE */ -INT vendorextnReadSection(PVOID pContext, PUCHAR pBuffer, enum bcm_flash2x_section_val SectionVal, - UINT offset, UINT numOfBytes) +INT vendorextnReadSection(PVOID pContext, PUCHAR pBuffer, + enum bcm_flash2x_section_val SectionVal, + UINT offset, UINT numOfBytes) { return STATUS_FAILURE; } @@ -112,8 +115,9 @@ INT vendorextnReadSection(PVOID pContext, PUCHAR pBuffer, enum bcm_flash2x_sect * Returns: * STATUS_SUCCESS/STATUS_FAILURE */ -INT vendorextnWriteSection(PVOID pContext, PUCHAR pBuffer, enum bcm_flash2x_section_val SectionVal, - UINT offset, UINT numOfBytes, BOOLEAN bVerify) +INT vendorextnWriteSection(PVOID pContext, PUCHAR pBuffer, + enum bcm_flash2x_section_val SectionVal, + UINT offset, UINT numOfBytes, BOOLEAN bVerify) { return STATUS_FAILURE; } @@ -135,8 +139,9 @@ INT vendorextnWriteSection(PVOID pContext, PUCHAR pBuffer, enum bcm_flash2x_sec * Returns: * STATUS_SUCCESS/STATUS_FAILURE */ -INT vendorextnWriteSectionWithoutErase(PVOID pContext, PUCHAR pBuffer, enum bcm_flash2x_section_val SectionVal, - UINT offset, UINT numOfBytes) +INT vendorextnWriteSectionWithoutErase(PVOID pContext, PUCHAR pBuffer, + enum bcm_flash2x_section_val SectionVal, + UINT offset, UINT numOfBytes) { return STATUS_FAILURE; } -- 1.7.9.5
_______________________________________________ Kernelnewbies mailing list [email protected] http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
