From: "Simon Sandström" <simon@nikanor.nu>
To: gregkh@linuxfoundation.org
Cc: =simon@nikanor.nu, jeremy@azazel.net, dan.carpenter@oracle.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
"Simon Sandström" <simon@nikanor.nu>
Subject: [PATCH 0/5] staging: kpc2000: remove unnecessary debug prints
Date: Mon, 10 Jun 2019 10:44:27 +0200 [thread overview]
Message-ID: <20190610084432.12597-1-simon@nikanor.nu> (raw)
These patches removes unnecessary debug prints in staging/kpc2000.
Debug prints that just informs about function entry or exit can be
removed as ftrace can be used to get this information.
Simon Sandström (5):
staging: kpc2000: remove unnecessary debug prints in cell_probe.c
staging: kpc2000: remove unnecessary debug prints in core.c
staging: kpc2000: remove unnecessary debug prints in dma.c
staging: kpc2000: remove unnecessary debug prints in fileops.c
staging: kpc2000: remove unnecessary debug prints in kpc_dma_driver.c
drivers/staging/kpc2000/kpc2000/cell_probe.c | 5 -----
drivers/staging/kpc2000/kpc2000/core.c | 6 ------
drivers/staging/kpc2000/kpc_dma/dma.c | 4 ----
drivers/staging/kpc2000/kpc_dma/fileops.c | 17 -----------------
.../staging/kpc2000/kpc_dma/kpc_dma_driver.c | 4 ----
5 files changed, 36 deletions(-)
--
2.20.1
next reply other threads:[~2019-06-10 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 8:44 Simon Sandström [this message]
2019-06-10 8:44 ` [PATCH 1/5] staging: kpc2000: remove unnecessary debug prints in cell_probe.c Simon Sandström
2019-06-10 8:44 ` [PATCH 2/5] staging: kpc2000: remove unnecessary debug prints in core.c Simon Sandström
2019-06-10 8:44 ` [PATCH 3/5] staging: kpc2000: remove unnecessary debug prints in dma.c Simon Sandström
2019-06-10 8:44 ` [PATCH 4/5] staging: kpc2000: remove unnecessary debug prints in fileops.c Simon Sandström
2019-06-10 8:44 ` [PATCH 5/5] staging: kpc2000: remove unnecessary debug prints in kpc_dma_driver.c Simon Sandström
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=20190610084432.12597-1-simon@nikanor.nu \
--to=simon@nikanor.nu \
--cc==simon@nikanor.nu \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jeremy@azazel.net \
--cc=linux-kernel@vger.kernel.org \
/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®