From: Leo Kim <leo.kim@atmel.com>
To: <gregkh@linuxfoundation.org>
Cc: <devel@driverdev.osuosl.org>, <linux-wireless@vger.kernel.org>,
<tony.cho@atmel.com>, <glen.lee@atmel.com>, <leo.kim@atmel.com>,
<austin.shin@atmel.com>, <Chris.Park@atmel.com>,
<adham.abozaeid@atmel.com>, <Nicolas.FERRE@atmel.com>
Subject: [PATCH 2/7] staging: wilc1000: wilc_spi.c: removes debug print log
Date: Tue, 15 Mar 2016 18:48:09 +0900 [thread overview]
Message-ID: <1458035294-13001-2-git-send-email-leo.kim@atmel.com> (raw)
In-Reply-To: <1458035294-13001-1-git-send-email-leo.kim@atmel.com>
This patches removes unnecessary debug print logs.
Signed-off-by: Leo Kim <leo.kim@atmel.com>
---
drivers/staging/wilc1000/wilc_spi.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/staging/wilc1000/wilc_spi.c b/drivers/staging/wilc1000/wilc_spi.c
index d41b8b6..4268e2f 100644
--- a/drivers/staging/wilc1000/wilc_spi.c
+++ b/drivers/staging/wilc1000/wilc_spi.c
@@ -196,9 +196,6 @@ static int wilc_spi_tx(struct wilc *wilc, u8 *b, u32 len)
dev_err(&spi->dev,
"can't write data with the following length: %d\n",
len);
- dev_err(&spi->dev,
- "FAILED due to NULL buffer or ZERO length check the following length: %d\n",
- len);
ret = -EINVAL;
}
--
1.9.1
next prev parent reply other threads:[~2016-03-15 9:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 9:48 [PATCH 1/7] staging: wilc1000: removes function 'init_tcp_tracking()' Leo Kim
2016-03-15 9:48 ` Leo Kim [this message]
2016-03-15 9:48 ` [PATCH 3/7] staging: wilc1000: removes duplicate vif variable setting Leo Kim
2016-03-15 9:48 ` [PATCH 4/7] staging: wilc1000: removes duplicate wilc " Leo Kim
2016-03-15 9:48 ` [PATCH 5/7] staging: wilc1000: changes an ambiguous debug messages Leo Kim
2016-03-15 9:48 ` [PATCH 6/7] staging: wilc1000: removes goto definitions from wilc_wlan_firmware_download Leo Kim
2016-03-15 9:48 ` [PATCH 7/7] staging: wilc1000: removes an unnecessary if-condition Leo Kim
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=1458035294-13001-2-git-send-email-leo.kim@atmel.com \
--to=leo.kim@atmel.com \
--cc=Chris.Park@atmel.com \
--cc=Nicolas.FERRE@atmel.com \
--cc=adham.abozaeid@atmel.com \
--cc=austin.shin@atmel.com \
--cc=devel@driverdev.osuosl.org \
--cc=glen.lee@atmel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tony.cho@atmel.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.