Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752306AbbBLVIx (ORCPT ); Thu, 12 Feb 2015 16:08:53 -0500 Received: from smtprelay0065.hostedemail.com ([216.40.44.65]:51131 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751325AbbBLVIw (ORCPT ); Thu, 12 Feb 2015 16:08:52 -0500 X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,joe@perches.com,:::::,RULES_HIT:41:355:379:541:599:960:968:973:988:989:1260:1277:1311:1313:1314:1345:1359:1373:1437:1515:1516:1518:1534:1542:1593:1594:1711:1730:1747:1777:1792:2198:2199:2393:2559:2562:2828:3138:3139:3140:3141:3142:3353:3622:3865:3866:3867:3868:3871:3872:4321:5007:6121:6261:6757:7903:10004:10400:10848:11026:11232:11658:11914:12043:12296:12517:12519:12740:13869:14093:14097:21080,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:fn,MSBL:0,DNSBL:none,Custom_rules:0:0:0 X-HE-Tag: heat68_2fff84d942545 X-Filterd-Recvd-Size: 3270 Message-ID: <1423775328.15343.38.camel@perches.com> Subject: Re: [PATCH 6/9] nbd: Restructure debugging prints From: Joe Perches To: Markus Pargmann Cc: nbd-general@lists.sourceforge.net, linux-kernel@vger.kernel.org Date: Thu, 12 Feb 2015 13:08:48 -0800 In-Reply-To: <1423774657-12748-7-git-send-email-mpa@pengutronix.de> References: <1423774657-12748-1-git-send-email-mpa@pengutronix.de> <1423774657-12748-7-git-send-email-mpa@pengutronix.de> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.12.7-0ubuntu1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2589 Lines: 69 On Thu, 2015-02-12 at 21:57 +0100, Markus Pargmann wrote: > dprintk has some name collisions with other frameworks and drivers. It > is also not necessary to have these custom debug print filters. Dynamic > debug offers the same amount of filtered debugging. > > This patch replaces all dprintks with dev_dbg(). It also removes the > ioctl dprintk which prints the ingoing ioctls which should be > replaceable by strace or similar stuff. Perhaps add #define nbd_dbg(nbd, fmt, ...) \ dev_dbg(disk_to_dev((nbd)->disk), "%s: " fmt, \ nbd->disk->disk_name, ##__VA_ARGS__) (or function with %pV) > diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c [] > +static void nbd_end_request(struct nbd_device *nbd, struct request *req) > { > int error = req->errors ? -EIO : 0; > struct request_queue *q = req->q; > unsigned long flags; > > - dprintk(DBG_BLKDEV, "%s: request %p: %s\n", req->rq_disk->disk_name, > - req, error ? "failed" : "done"); > + dev_dbg(disk_to_dev(nbd->disk), "%s: request %p: %s\n", > + req->rq_disk->disk_name, req, error ? "failed" : "done"); so this becomes nbd_dbg(nbd, "request %p: %s\n", req, error ? "failed" : "done"); > @@ -276,11 +239,9 @@ static int nbd_send_req(struct nbd_device *nbd, struct request *req) > } > memcpy(request.handle, &req, sizeof(req)); > > - dprintk(DBG_TX, "%s: request %p: sending control (%s@%llu,%uB)\n", > - nbd->disk->disk_name, req, > - nbdcmd_to_ascii(nbd_cmd(req)), > - (unsigned long long)blk_rq_pos(req) << 9, > - blk_rq_bytes(req)); > + dev_dbg(disk_to_dev(nbd->disk), "%s: request %p: sending control (%s@%llu,%uB)\n", > + nbd->disk->disk_name, req, nbdcmd_to_ascii(nbd_cmd(req)), > + (unsigned long long)blk_rq_pos(req) << 9, blk_rq_bytes(req)); nbd_dbg(nbd, "request %p: sending control (%s@%llu,%uB)\n", req, nbdcmd_to_ascii(nbd_cmd(req)), (unsigned long long)blk_rq_pos(req) << 9, blk_rq_bytes(req)); > @@ -300,8 +261,8 @@ static int nbd_send_req(struct nbd_device *nbd, struct request *req) > flags = 0; > if (!rq_iter_last(bvec, iter)) > flags = MSG_MORE; > - dprintk(DBG_TX, "%s: request %p: sending %d bytes data\n", > - nbd->disk->disk_name, req, bvec.bv_len); > + dev_dbg(disk_to_dev(nbd->disk), "%s: request %p: sending %d bytes data\n", > + nbd->disk->disk_name, req, bvec.bv_len); etc... -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/