From: Jens Axboe <axboe@suse.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Borislav Petkov <bbpetkov@yahoo.de>,
linux-ide@vger.kernel.org, htejun@gmail.com,
randy_d_dunlap@linux.intel.com
Subject: Re: PATCH convert libata-core to the new debugging scheme
Date: Wed, 25 Jan 2006 16:13:44 +0100 [thread overview]
Message-ID: <20060125151343.GE4212@suse.de> (raw)
In-Reply-To: <20060125150646.GC14225@havoc.gtf.org>
On Wed, Jan 25 2006, Jeff Garzik wrote:
> On Wed, Jan 25, 2006 at 04:04:04PM +0100, Bartlomiej Zolnierkiewicz wrote:
> > On 1/24/06, Jeff Garzik <jgarzik@pobox.com> wrote:
> > > On Tue, Jan 24, 2006 at 08:43:43PM +0100, Borislav Petkov wrote:
> > > > for the debugging macros which to me _is_ kinda too much. In addition, the
> > > > ata_msg_xxx() macros are going to be pretty useless if we wrap them one more
> > > > time into other macros but this is only my opinion.
> > >
> > > Yes, I like the current stuff, and am not really interested in further
> > > macros.
> >
> > What about using Randy's suggestion the other way around:
> > embedding printk-s into ata_msg_* macros?
> >
> > This way we would get rid of all these if-s in the code
> > without adding more macros.
> >
> > i.e. we would have
> >
> > + ata_msg_ctl(ap, "ata%u: cmd 0x%X\n", ap->id, tf->command);
> >
> > instead of
> >
> > + if (ata_msg_ctl(ap))
> > + printk(KERN_DEBUG "%s: ata%u: cmd 0x%X\n",
> > + __FUNCTION__, ap->id, tf->command);
>
> Those are the further macros that I was objecting to...
>
> The current ata_msg_ctl() style macros are in the kernel, and thus
> accepted.
It looks cleaner, though. printk() lines are usually the worst to keep
from wrapping, saving a tab indentation there seems like it would be
worth it imho.
--
Jens Axboe
next prev parent reply other threads:[~2006-01-25 15:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 19:43 PATCH convert libata-core to the new debugging scheme Borislav Petkov
2006-01-24 19:47 ` Jeff Garzik
2006-01-25 15:04 ` Bartlomiej Zolnierkiewicz
2006-01-25 15:06 ` Jeff Garzik
2006-01-25 15:13 ` Jens Axboe [this message]
2006-01-25 15:12 ` Jeff Garzik
2006-01-25 15:16 ` Jens Axboe
[not found] <20060117105702.5e5a5cb5.randy_d_dunlap@linux.intel.com>
2006-01-24 9:07 ` Borislav Petkov
2006-01-24 13:08 ` Tejun Heo
2006-01-24 16:30 ` Randy Dunlap
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=20060125151343.GE4212@suse.de \
--to=axboe@suse.de \
--cc=bbpetkov@yahoo.de \
--cc=bzolnier@gmail.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=randy_d_dunlap@linux.intel.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).