public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Shailendra Verma <shailendra.capricorn@gmail.com>,
	Kalle Valo <kvalo@codeaurora.org>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net:wireless - Change 1 to true for bool type variable.
Date: Mon, 25 May 2015 13:06:07 -0500	[thread overview]
Message-ID: <5563648F.106@lwfinger.net> (raw)
In-Reply-To: <1432576544-3639-1-git-send-email-shailendra.capricorn@gmail.com>

On 05/25/2015 12:55 PM, Shailendra Verma wrote:
> The variable translate is bool type.So assigning true instead of 1.
>
> Signed-off-by: Shailendra Verma <shailendra.capricorn@gmail.com>

When you submit a patch for a particular driver in the drivers/net/wireless/ 
tree, it is preferred that the subject start with the driver name, not with 
net:wireless. Accordingly, your subject should be "ray_cs: Change 1 to true for 
bool type variable". In fact, you can probably choose a better wording for the 
rest of the title, but I do not insist.

Among other advantages, this choice of subject allows easy searches for patches 
for a given driver using 'git log'.

Larry

> ---
>   drivers/net/wireless/ray_cs.c |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/wireless/ray_cs.c b/drivers/net/wireless/ray_cs.c
> index 477f863..0881ba8 100644
> --- a/drivers/net/wireless/ray_cs.c
> +++ b/drivers/net/wireless/ray_cs.c
> @@ -143,7 +143,7 @@ static int psm;
>   static char *essid;
>
>   /* Default to encapsulation unless translation requested */
> -static bool translate = 1;
> +static bool translate = true;
>
>   static int country = USA;
>
>


  reply	other threads:[~2015-05-25 18:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-25 17:55 [PATCH] net:wireless - Change 1 to true for bool type variable Shailendra Verma
2015-05-25 18:06 ` Larry Finger [this message]
2015-05-25 18:11 ` Joe Perches

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=5563648F.106@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shailendra.capricorn@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