public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Harsh Kumar <harsh1kumar@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [Patch] Staging: winbond: Made local functions static
Date: Thu, 30 May 2013 13:33:48 +0000	[thread overview]
Message-ID: <51A7526C.9090907@gmail.com> (raw)
In-Reply-To: <51A6E81C.2000303@gmail.com>



On Thursday 30 May 2013 06:38 PM, Dan Carpenter wrote:
> Hi Harsh,
> 
> Here are some notes on the devel process.
> 
> You should probably include the driver devel list in the CC.  I
> always include one public development mailing list.  Normally I
> don't include LKML if I have another devel list CC'd.
> 
> In staging we're trying to merge patches as fast as we can so our
> standards are slightly lower than things in the mm/ directory for
> example.
> 
> Your last two patches have had too many unrelated whitespace changes
> mixed in.  They were small and this is staging so no one commented
> on it.  But it's best to avoid that.
> 
> When someone gives a review comment like my comment on u8 vs int or
> Walter's comment on Set_ChanIndep_RfData_al7230_50(), that's not
> stuff you introduced so it could be fixed later/ignored.
> 
> Walter's comment on "inline" is correct, but it's probably not a
> "redo this patch" thing, it's more of a "think about this for later"
> thing.  In mm/ that kind of thing would be more serious, but this is
> staging.
> 

Thanks for the guidance, I will take care of this in future.

> My comment on deleting blank lines is something that the patch
> introduced.  We'll need to put the blank lines back for this patch
> to move out of staging.  It would be better if you could send a v2
> patch, but Pavel already Acked the patch and Greg may have merged
> it.

Thanks for the clarifications Dan, I was not able to decide what 
to do - submit a new patch or not.
The v2 patch will be over & above the changes that have been by my previous 
patch, right?

Harsh

> 
> Anyway, thank you for the patches.  I hope you'll stick around. :)
> 
> regards,
> dan carpenter
> 





  parent reply	other threads:[~2013-05-30 13:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30  5:48 [Patch] Staging: winbond: Made local functions static Harsh Kumar
2013-05-30  9:20 ` walter harms
2013-05-30  9:40 ` Pavel Machek
2013-05-30 12:13 ` Dan Carpenter
2013-05-30 12:18 ` Dan Carpenter
2013-05-30 13:08 ` Dan Carpenter
2013-05-30 13:33 ` Harsh Kumar [this message]
2013-05-30 13:58 ` Dan Carpenter

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=51A7526C.9090907@gmail.com \
    --to=harsh1kumar@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    /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