mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Parth Sane <laerdevstudios@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Larry.Finger@lwfinger.net, florian.c.schilhabel@googlemail.com,
	luisbg@osg.samsung.com,
	"open list:STAGING SUBSYSTEM" <devel@driverdev.osuosl.org>,
	linux-kernel@vger.kernel.org, amitoj1606@gmail.com
Subject: Re: [PATCH] staging: rtl8712: Fixed Multiple Parenthesis Alignment
Date: Sun, 20 Mar 2016 21:21:26 +0530	[thread overview]
Message-ID: <0EF3C6FE-993D-4661-9595-8135ADEF1488@gmail.com> (raw)
In-Reply-To: <1458488880.4228.37.camel@perches.com>

[-- Attachment #1: Type: text/plain, Size: 1865 bytes --]


> On 20-Mar-2016, at 9:18 PM, Joe Perches <joe@perches.com> wrote:
> 
> On Sun, 2016-03-20 at 14:33 +0000, Parth Sane wrote:
>> Fixed multiple parenthesis alignment warnings.
>> Signed-off-by: Parth Sane <laerdevstudios@gmail.com>
> 
> Please always add a blank line after your changelog and
> before your "Signed-off-by:" line
> 
>> diff --git a/drivers/staging/rtl8712/hal_init.c b/drivers/staging/rtl8712/hal_init.c
> []
>> @@ -197,7 +197,7 @@ static u8 rtl8712_dl_fw(struct _adapter *padapter)
>>  						       0x0000ffff);
>>  			memcpy(ppayload, ptr, dump_imem_sz);
>>  			r8712_write_mem(padapter, RTL8712_DMA_VOQ,
>> -				  dump_imem_sz + TXDESC_SIZE,
>> +					dump_imem_sz + TXDESC_SIZE,
>>  				  (u8 *)ptx_desc);
> 
> Please align all lines of multi-line statements.
> 
> checkpatch is a stupid little script.
> You have to make sure your own patches are sensible.
> 
> There are several things you should read and
> understand in the Documentation directory.
> 
> 	Documentation/CodingStyle
> 	Documentation/SubmittingPatches
> 	Documentation/SubmitChecklist
> 
> Fixing checkpatch messages is sometimes a decent
> way to understand this process, but the patches
> that can be generated fixing these messages tend
> to have low overall value.
> 
> After doing a few of these, please move on to
> some part of the kernel that interests you and
> submit new code or start to fix actual defects.
> 
> Maybe if you are interested in wireless drivers,
> buy a NIC that isn't supported by the mac80211
> drivers and adapt the existing staging driver for
> that variant.
> 
> Code, test, validate, submit, repeat...
> 
Hi,
I’m first trying my hands at easy stuff before I actually move on to more difficult stuff. I will surely look in that direction. Thanks for your valuable inputs.
Regards,
Parth Sane

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]

  reply	other threads:[~2016-03-20 15:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-20 14:33 Parth Sane
2016-03-20 15:48 ` Joe Perches
2016-03-20 15:51   ` Parth Sane [this message]
     [not found]     ` <CAEE9rjYEj98=riyLLrWg9ErLwVV5sMbT27MpZ2-UajUC066AQw@mail.gmail.com>
2016-03-20 16:49       ` Parth Sane

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0EF3C6FE-993D-4661-9595-8135ADEF1488@gmail.com \
    --to=laerdevstudios@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=amitoj1606@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=florian.c.schilhabel@googlemail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luisbg@osg.samsung.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®