Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Kieran Bingham <kbingham@kernel.org>
To: niklas.soderlund@ragnatech.se
Cc: linux-renesas-soc@vger.kernel.org,
	kieran.bingham@ideasonboard.com,
	Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Subject: [PATCH 1/3] tools: 8camera-status: Fix write failure mis-allocations
Date: Wed, 15 Nov 2017 14:38:29 +0000	[thread overview]
Message-ID: <1510756711-6488-2-git-send-email-kbingham@kernel.org> (raw)
In-Reply-To: <1510756711-6488-1-git-send-email-kbingham@kernel.org>

From: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>

Debug prints of the max9271_write call are appearing in the failure counts.

Fix the 'catcher' so that it is more specific to the failure

Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
---
 tools/8camera-status | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/8camera-status b/tools/8camera-status
index 234b8a0cab2b..cdfe76ef286f 100755
--- a/tools/8camera-status
+++ b/tools/8camera-status
@@ -21,7 +21,7 @@ BEGIN {
 	print
 }
 
-/max9271_write/ {
+/max9271_write.*write failed/ {
 	max9271_write_fail++
 	print
 }
-- 
2.7.4

  reply	other threads:[~2017-11-15 14:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-15 14:38 [PATCH 0/3] [VIN-Tests] minor updates Kieran Bingham
2017-11-15 14:38 ` Kieran Bingham [this message]
2017-11-15 16:31   ` [PATCH 1/3] tools: 8camera-status: Fix write failure mis-allocations Niklas Söderlund
2017-11-15 14:38 ` [PATCH 2/3] tools: 8camera-status: Expand to 9 cameras Kieran Bingham
2017-11-15 16:31   ` Niklas Söderlund
2017-11-15 14:38 ` [PATCH 3/3] vin-tests: Refactor mc_get_dev Kieran Bingham
2017-11-15 16:51   ` Niklas Söderlund
2017-11-16 10:54     ` Kieran Bingham

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=1510756711-6488-2-git-send-email-kbingham@kernel.org \
    --to=kbingham@kernel.org \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=niklas.soderlund@ragnatech.se \
    /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