From: Dan Carpenter <dan.carpenter@oracle.com>
To: Adithya K <linux.challenge1@gmail.com>
Cc: standby24x7@gmail.com, khoroshilov@ispras.ru, arnd@arndb.de,
burzalodowa@gmail.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH] Staging: gdm72xx Fix minor coding style problems
Date: Thu, 8 May 2014 10:59:13 +0300 [thread overview]
Message-ID: <20140508075913.GX4963@mwanda> (raw)
In-Reply-To: <1399530237-1788-1-git-send-email-user@akrishna-Latitude-E6430>
On Thu, May 08, 2014 at 11:53:57AM +0530, Adithya K wrote:
> This is patch for fixing of minor coding style problems.
>
> Signed-off-by: Adithya K <linux.challenge1@gmail.com>
> ---
> drivers/staging/gdm72xx/gdm_qos.c | 3 ++-
> drivers/staging/gdm72xx/gdm_sdio.c | 1 +
> drivers/staging/gdm72xx/gdm_usb.c | 2 +-
> drivers/staging/gdm72xx/gdm_wimax.c | 3 +++
> drivers/staging/gdm72xx/usb_boot.c | 1 +
> 5 files changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/gdm72xx/gdm_qos.c b/drivers/staging/gdm72xx/gdm_qos.c
> index 50d43ad..5ed32b9 100644
> --- a/drivers/staging/gdm72xx/gdm_qos.c
> +++ b/drivers/staging/gdm72xx/gdm_qos.c
> @@ -229,6 +229,7 @@ static u32 extract_qos_list(struct nic *nic, struct list_head *head)
> entry = list_entry(
> qcb->qos_list[i].prev,
> struct qos_entry_s, list);
> +
> list_move_tail(&entry->list, head);
> qcb->csr[i].qos_buf_count++;
>
This one is wrong. It's not something I care about but since the patch
needs to be redone, then please leave it out.
> diff --git a/drivers/staging/gdm72xx/gdm_usb.c b/drivers/staging/gdm72xx/gdm_usb.c
> index 20539d8..8fd1b1f 100644
> --- a/drivers/staging/gdm72xx/gdm_usb.c
> +++ b/drivers/staging/gdm72xx/gdm_usb.c
> @@ -759,7 +759,7 @@ static int k_mode_thread(void *arg)
> spin_lock_irqsave(&k_lock, flags2);
> }
> wait_event_interruptible_lock_irq(k_wait,
> - !list_empty(&k_list) || k_mode_stop,
> + !list_empty(&k_list) || k_mode_stop,
> k_lock);
> spin_unlock_irqrestore(&k_lock, flags2);
> }
This one is totally wrong. Please resend withouth this chunk.
regards,
dan carpenter
prev parent reply other threads:[~2014-05-08 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 6:23 [PATCH] Staging: gdm72xx Fix minor coding style problems Adithya K
2014-05-08 6:40 ` Joe Perches
2014-05-08 8:01 ` Dan Carpenter
2014-05-08 7:59 ` Dan Carpenter [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=20140508075913.GX4963@mwanda \
--to=dan.carpenter@oracle.com \
--cc=arnd@arndb.de \
--cc=burzalodowa@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=khoroshilov@ispras.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.challenge1@gmail.com \
--cc=standby24x7@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