From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Mohammad Jamal <md.jamalmohiuddin@gmail.com>,
varkabhadram@gmail.com, alex.aring@gmail.com,
linux-wpan@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: ieee802154: cc2520: Fix coding style issues
Date: Fri, 23 Jan 2015 15:37:46 +0300 [thread overview]
Message-ID: <54C2409A.6020506@cogentembedded.com> (raw)
In-Reply-To: <1422005180-13230-1-git-send-email-md.jamalmohiuddin@gmail.com>
Hello.
On 1/23/2015 12:26 PM, Mohammad Jamal wrote:
> This patch solves the coding style issues such as space after ,
s/after/before/?
> and removes the blank lines
Extra blank lines, you mean?
> Signed-off-by: Mohammad Jamal <md.jamalmohiuddin@gmail.com>
> ---
> drivers/net/ieee802154/cc2520.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
> diff --git a/drivers/net/ieee802154/cc2520.c b/drivers/net/ieee802154/cc2520.c
> index f9df9fa..dd129be 100644
> --- a/drivers/net/ieee802154/cc2520.c
> +++ b/drivers/net/ieee802154/cc2520.c
[...]
> @@ -551,14 +550,14 @@ cc2520_ed(struct ieee802154_hw *hw, u8 *level)
> u8 rssi;
> int ret;
>
> - ret = cc2520_read_register(priv , CC2520_RSSISTAT, &status);
> + ret = cc2520_read_register(priv, CC2520_RSSISTAT, &status);
> if (ret)
> return ret;
>
> if (status != RSSI_VALID)
> return -EINVAL;
>
> - ret = cc2520_read_register(priv , CC2520_RSSI, &rssi);
> + ret = cc2520_read_register(priv, CC2520_RSSI, &rssi);
[...]
WBR, Sergei
next prev parent reply other threads:[~2015-01-23 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 9:26 [PATCH] net: ieee802154: cc2520: Fix coding style issues Mohammad Jamal
2015-01-23 9:39 ` Varka Bhadram
2015-01-23 12:37 ` Sergei Shtylyov [this message]
2015-01-23 12:44 ` Jamal Mohammad
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=54C2409A.6020506@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=alex.aring@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=md.jamalmohiuddin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=varkabhadram@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.