All of lore.kernel.org
 help / color / mirror / Atom feed
From: robin.krahl@ireas.org (Robin Krahl)
To: kernelnewbies@lists.kernelnewbies.org
Subject: bcm2835-audio: logging mechanism
Date: Wed, 8 Mar 2017 09:16:07 +0100	[thread overview]
Message-ID: <20170308081607.GA2335@spectator> (raw)
In-Reply-To: <20170308045835.GA3455@kroah.com>

On 2017-03-08 05:58:35, Greg KH wrote:
> On Wed, Mar 08, 2017 at 12:52:38AM +0100, Robin Krahl wrote:
> > So my question is:  Does it make sense to replace the audio_* and LOG_*
> > macros with the standard dev_* functions?
> 
> Yes.
> 
> > And is it okay to remove log messages like "IN" and "OUT" that are
> > only used to track function entries and exits?
> 
> Yes please!

Thanks!  I?ll prepare a patch.

Robin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170308/fa187f17/attachment.bin 

      reply	other threads:[~2017-03-08  8:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07 23:52 bcm2835-audio: logging mechanism Robin Krahl
2017-03-08  4:58 ` Greg KH
2017-03-08  8:16   ` Robin Krahl [this message]

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=20170308081607.GA2335@spectator \
    --to=robin.krahl@ireas.org \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.