mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Greg KH <greg@kroah.com>
Cc: "Mark Rankilor" <reodge@gmail.com>,
	devel@driverdev.osuosl.org, "Henri Häkkinen" <henuxd@gmail.com>,
	gregkh@suse.de, andrea.gelmini@gelma.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging:comedi: Fixed coding convention issues.
Date: Thu, 17 Jun 2010 16:15:58 -0700	[thread overview]
Message-ID: <1276816558.1005.93.camel@Joe-Laptop.home> (raw)
In-Reply-To: <20100617225108.GA32334@kroah.com>

On Thu, 2010-06-17 at 15:51 -0700, Greg KH wrote:
> On Sat, Jun 12, 2010 at 10:30:50PM -0700, Joe Perches wrote:
> > On Sat, 2010-06-12 at 22:07 -0700, Joe Perches wrote:
> > > 2: Create some comedi logging functions or macros like:
> > >    	comedi_<level>(fmt, arg...) (ie: comedi_info, comedi_err, etc)
> > >    where "comedi:" is always prefixed and an
> > >    optional #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
> > >    could be used.

> I would prefer the conversion of everything over to the dev_printk()
> versions instead of creating a new macro for every individual subsystem.
> That way you get the advantage of logging everything in the common
> format and the dynamic debug functionality as well.

What I posted has dynamic_debug.

+#elif defined(CONFIG_DYNAMIC_DEBUG)
+/* dynamic_pr_debug() uses pr_fmt() internally so we don't need it here */
+#define comedi_debug(fmt, ...)                         \
+       dynamic_pr_debug(fmt, ##__VA_ARGS__)

As far as I know, comedi doesn't always take a struct device *.
I believe it's only used when there's a DMA.

In struct comedi_device, there are two struct device *'s.

	struct device *class_dev;
...
	struct device *hw_dev;



  reply	other threads:[~2010-06-17 23:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-12 10:14 Henri Häkkinen
2010-06-13  2:14 ` Mark Rankilor
2010-06-13  5:07   ` Joe Perches
2010-06-13  5:30     ` Joe Perches
2010-06-13 11:27       ` Henri Häkkinen
2010-06-13 18:11         ` Joe Perches
2010-06-17 22:51       ` Greg KH
2010-06-17 23:15         ` Joe Perches [this message]
2010-06-17 23:28           ` Greg KH
2010-06-17 23:47             ` Joe Perches
2010-06-18 12:16               ` Ian Abbott
2010-06-12 11:04 Henri Häkkinen
2010-06-14  6:34 Henri Häkkinen
2010-06-17 23:02 ` Greg KH

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=1276816558.1005.93.camel@Joe-Laptop.home \
    --to=joe@perches.com \
    --cc=andrea.gelmini@gelma.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=henuxd@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reodge@gmail.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

all inboxes | Powered by JetHome®