Linux wireless drivers development
 help / color / mirror / Atom feed
From: Vaishali Thakkar <vaishali.thakkar@oracle.com>
To: vaibhavddit@gmail.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] Fixing Style Problems
Date: Mon, 27 Mar 2017 12:57:37 +0530	[thread overview]
Message-ID: <dd4b66c5-d835-4b1d-14ee-2c67799e8f72@oracle.com> (raw)
In-Reply-To: <1490596579-22039-1-git-send-email-vaibhavddit@gmail.com>

On Monday 27 March 2017 12:06 PM, vaibhavddit@gmail.com wrote:
> From: Vaibhav Kothari <vaibhavddit@gmail.com>
>
> - Corrected 80 characters column width

Hi,

There are very high chances that this patch will be ignored.
Mainly because you have not CC'ed proper mailing lists and
maintainers.

I'm just mentioning few things which this patch is lacking:

- Proper Subject and commit log
- Use of scripts/get_maintainer.pl for getting the list of mailing
   lists and maintainers
- The change itself doesn't look correct, most of the time we advise
   newbies to avoid sending patches for 80 characters line warning as
   original author might have some reason for not doing that change.

You can use this[1] and this[2] to improve your patch.

Thanks!

[1] https://kernelnewbies.org/FirstKernelPatch
[2] https://kernelnewbies.org/PatchPhilosophy

> Signed-off-by: Vaibhav Kothari <vaibhavddit@gmail.com>
> ---
>  drivers/staging/wilc1000/coreconfigurator.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/wilc1000/coreconfigurator.h b/drivers/staging/wilc1000/coreconfigurator.h
> index 5256f40..794104b 100644
> --- a/drivers/staging/wilc1000/coreconfigurator.h
> +++ b/drivers/staging/wilc1000/coreconfigurator.h
> @@ -123,7 +123,7 @@ struct disconnect_info {
>  s32 wilc_parse_network_info(u8 *msg_buffer,
>  			    struct network_info **ret_network_info);
>  s32 wilc_parse_assoc_resp_info(u8 *buffer, u32 buffer_len,
> -			       struct connect_resp_info **ret_connect_resp_info);
> +			      struct connect_resp_info **ret_connect_resp_info);
>  void wilc_scan_complete_received(struct wilc *wilc, u8 *buffer, u32 length);
>  void wilc_network_info_received(struct wilc *wilc, u8 *buffer, u32 length);
>  void wilc_gnrl_async_info_received(struct wilc *wilc, u8 *buffer, u32 length);
>

      reply	other threads:[~2017-03-27  7:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <[PATCH 1/1] Fixing Coding style problems>
2017-03-27  6:36 ` [PATCH] Fixing Style Problems vaibhavddit
2017-03-27  7:27   ` Vaishali Thakkar [this message]

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=dd4b66c5-d835-4b1d-14ee-2c67799e8f72@oracle.com \
    --to=vaishali.thakkar@oracle.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=vaibhavddit@gmail.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