From: Fabio Falzoi <fabio.falzoi84@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
micky_ching@realsil.com.cn, wei_wang@realsil.com.cn,
joe@perches.org, Fabio Falzoi <fabio.falzoi84@gmail.com>
Subject: [PATCH v6 0/2] Staging: rts5208: Use standard debug features
Date: Tue, 5 Aug 2014 23:24:16 +0200 [thread overview]
Message-ID: <1407273858-15267-1-git-send-email-fabio.falzoi84@gmail.com> (raw)
Use standard debug features instead of relying on the custom
configuration option CONFIG_RTS5208_DEBUG and a series of home grown
macros.
This new version contains the remaining two chunks of the v5 patchset:
the first two chunks have already been merged.
Changes in v6:
* Use print_hex_dump_bytes in place of dev_dbg to dump buffer potentially
larger than 64 bytes.
Changes in v5:
* remove useless prints used just to mark when entering a function
(we should prefer ftrace for that)
Changes in v4:
* use dev_dbg instead of pr_debug
* use dev_dbg with %*ph modifier instead of print_hex_dump_bytes
Changes in v3:
* defined rtsx_hex_dump as a static inline function to avoid checkpatch errors
Changes in v2:
* defined rtsx_hex_dump macro to produce output only if DEBUG is defined
Fabio Falzoi (2):
Staging: rts5208: Use dev_dbg and print_hex_dump_bytes to dump memory
Staging: rts5208: Remove CONFIG_RTS5208_DEBUG option
drivers/staging/rts5208/Kconfig | 7 -------
drivers/staging/rts5208/ms.c | 5 +++--
drivers/staging/rts5208/rtsx_chip.c | 6 ++++--
drivers/staging/rts5208/rtsx_scsi.c | 7 +++----
drivers/staging/rts5208/sd.c | 11 ++++-------
drivers/staging/rts5208/trace.h | 8 --------
6 files changed, 14 insertions(+), 30 deletions(-)
--
2.0.0
next reply other threads:[~2014-08-05 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 21:24 Fabio Falzoi [this message]
2014-08-05 21:24 ` [PATCH v6 1/2] Staging: rts5208: Use dev_dbg and print_hex_dump_bytes to dump memory Fabio Falzoi
2014-08-05 21:24 ` [PATCH v6 2/2] Staging: rts5208: Remove CONFIG_RTS5208_DEBUG option Fabio Falzoi
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=1407273858-15267-1-git-send-email-fabio.falzoi84@gmail.com \
--to=fabio.falzoi84@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.org \
--cc=linux-kernel@vger.kernel.org \
--cc=micky_ching@realsil.com.cn \
--cc=wei_wang@realsil.com.cn \
/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
all inboxes | Powered by JetHome®