linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@zonque.org>
To: sameo@linux.intel.com
Cc: linux-wireless@vger.kernel.org, colin.king@canonical.com,
	shikha.singh@st.com, Daniel Mack <daniel@zonque.org>
Subject: [PATCH v3 04/11] NFC: st95hf: remove logging from spi functions
Date: Tue, 24 Jul 2018 11:59:34 +0200	[thread overview]
Message-ID: <20180724095941.25777-5-daniel@zonque.org> (raw)
In-Reply-To: <20180724095941.25777-1-daniel@zonque.org>

The callers of these functions already log on errors, and there's no
need to do it from two places.

Signed-off-by: Daniel Mack <daniel@zonque.org>
---
 drivers/nfc/st95hf/spi.c | 19 ++++---------------
 1 file changed, 4 insertions(+), 15 deletions(-)

diff --git a/drivers/nfc/st95hf/spi.c b/drivers/nfc/st95hf/spi.c
index e2d3bbcc8c34..d5894d4546b1 100644
--- a/drivers/nfc/st95hf/spi.c
+++ b/drivers/nfc/st95hf/spi.c
@@ -47,8 +47,6 @@ int st95hf_spi_send(struct st95hf_spi_context *spicontext,
 
 	result = spi_sync(spidev, &m);
 	if (result) {
-		dev_err(&spidev->dev, "error: sending cmd to st95hf using SPI = %d\n",
-			result);
 		mutex_unlock(&spicontext->spi_lock);
 		return result;
 	}
@@ -62,12 +60,10 @@ int st95hf_spi_send(struct st95hf_spi_context *spicontext,
 	result = wait_for_completion_timeout(&spicontext->done,
 					     msecs_to_jiffies(1000));
 	/* check for timeout or success */
-	if (!result) {
-		dev_err(&spidev->dev, "error: response not ready timeout\n");
+	if (!result)
 		result = -ETIMEDOUT;
-	} else {
+	else
 		result = 0;
-	}
 
 	mutex_unlock(&spicontext->spi_lock);
 
@@ -79,7 +75,7 @@ EXPORT_SYMBOL_GPL(st95hf_spi_send);
 int st95hf_spi_recv_response(struct st95hf_spi_context *spicontext,
 			     unsigned char *receivebuff)
 {
-	int len = 0;
+	int ret, len;
 	struct spi_transfer tx_takedata;
 	struct spi_message m;
 	struct spi_device *spidev = spicontext->spidev;
@@ -89,8 +85,6 @@ int st95hf_spi_recv_response(struct st95hf_spi_context *spicontext,
 		{.rx_buf = receivebuff, .len = 2, .cs_change = 1,},
 	};
 
-	int ret = 0;
-
 	memset(&tx_takedata, 0x0, sizeof(struct spi_transfer));
 
 	mutex_lock(&spicontext->spi_lock);
@@ -102,8 +96,6 @@ int st95hf_spi_recv_response(struct st95hf_spi_context *spicontext,
 
 	ret = spi_sync(spidev, &m);
 	if (ret) {
-		dev_err(&spidev->dev, "spi_recv_resp, data length error = %d\n",
-			ret);
 		mutex_unlock(&spicontext->spi_lock);
 		return ret;
 	}
@@ -127,11 +119,8 @@ int st95hf_spi_recv_response(struct st95hf_spi_context *spicontext,
 	ret = spi_sync(spidev, &m);
 
 	mutex_unlock(&spicontext->spi_lock);
-	if (ret) {
-		dev_err(&spidev->dev, "spi_recv_resp, data read error = %d\n",
-			ret);
+	if (ret)
 		return ret;
-	}
 
 	return len;
 }
-- 
2.17.1

  parent reply	other threads:[~2018-07-24 11:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24  9:59 [PATCH v3 00/11] NFC: A bunch of cleanups for st95hf Daniel Mack
2018-07-24  9:59 ` [PATCH v3 01/11] Revert "NFC: st95hf: drop illegal kfree_skb()" Daniel Mack
2018-07-24  9:59 ` [PATCH v3 02/11] NFC: st95hf: drop nfcdev_free Daniel Mack
2018-07-24  9:59 ` [PATCH v3 03/11] NFC: st95hf: drop illegal kfree_skb() in IRQ handler Daniel Mack
2018-07-24  9:59 ` Daniel Mack [this message]
2018-07-24  9:59 ` [PATCH v3 05/11] NFC: st95hf: remove exchange_lock Daniel Mack
2018-07-24  9:59 ` [PATCH v3 06/11] NFC: st95hf: move skb allocation to ISR Daniel Mack
2018-07-24  9:59 ` [PATCH v3 07/11] NFC: st95hf: ignore spurious interrupts Daniel Mack
2018-07-24  9:59 ` [PATCH v3 08/11] NFC: st95hf: re-order command defines Daniel Mack
2018-07-24  9:59 ` [PATCH v3 09/11] NFC: st95hf: unify sync/async flags Daniel Mack
2018-07-24  9:59 ` [PATCH v3 10/11] NFC: st95hf: two small style nits Daniel Mack
2018-07-24  9:59 ` [PATCH v3 11/11] NFC: st95hf: add of match table Daniel Mack
2018-08-06 10:38 ` [PATCH v3 00/11] NFC: A bunch of cleanups for st95hf Daniel Mack
2018-09-18 10:04   ` Daniel Mack

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=20180724095941.25777-5-daniel@zonque.org \
    --to=daniel@zonque.org \
    --cc=colin.king@canonical.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    --cc=shikha.singh@st.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;
as well as URLs for NNTP newsgroup(s).