All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Raymond Yau <superquad.vortex2@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Joe Perches <joe@perches.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH v2 2/2] ALSA: au88x0: pr_* replaced with dev_*
Date: Fri, 17 Oct 2014 09:02:17 +0530	[thread overview]
Message-ID: <20141017033217.GA3554@sudip-PC> (raw)
In-Reply-To: <s5h61fkw2k7.wl-tiwai@suse.de>

On Thu, Oct 16, 2014 at 03:45:44PM +0200, Takashi Iwai wrote:
> At Thu, 16 Oct 2014 11:04:34 +0800,
> Raymond Yau wrote:
<snip>
> > > > since these 2 commits:
> > > >
> > > > commit e28d713704117bca0820c732210df6075b09f13b
> > > > Author: Linus Torvalds <torvalds@linux-foundation.org>
> > > > Date:   Tue Jun 16 11:02:28 2009 -0700
> > > >
> > > >     printk: Add KERN_DEFAULT printk log-level
> > > >
> > > >     This adds a KERN_DEFAULT loglevel marker, for when you cannot decide
> > > >     which loglevel you want, and just want to keep an existing printk
> > > >     with the default loglevel.
> > > >
> > > >     The difference between having KERN_DEFAULT and having no log-level
> > > >     marker at all is two-fold:
> > > >
> > > >      - having the log-level marker will now force a new-line if the
> > > >        previous printout had not added one (perhaps because it forgot,
> > > >        but perhaps because it expected a continuation)
> > > >
> > > >      - having a log-level marker is required if you are printing out a
> > > >        message that otherwise itself could perhaps otherwise be mistaken
> > > >        for a log-level.
> > > >
> > > > and
> > > >
> > > > commit 5fd29d6ccbc98884569d6f3105aeca70858b3e0f
> > > > Author: Linus Torvalds <torvalds@linux-foundation.org>
> > > > Date:   Tue Jun 16 10:57:02 2009 -0700
> > > >
> > > >     printk: clean up handling of log-levels and newlines
> > > >
> > > >     It used to be that we would only look at the log-level in a printk()
> > > >     after explicit newlines, which can cause annoying problems when the
> > > >     previous printk() did not end with a '\n'. In that case, the
> > log-level
> > > >     marker would be just printed out in the middle of the line, and be
> > > >     seen as just noise rather than change the logging level.
> > > >
> > > >     This changes things to always look at the log-level in the first
> > > >     bytes of the printout. If a log level marker is found, it is always
> > > >     used as the log-level. Additionally, if no newline existed, one is
> > > >     added (unless the log-level is the explicit KERN_CONT marker, to
> > > >     explicitly show that it's a continuation of a previous line).
> > > >
> > > >
> > > >
> > 
> > Do the driver still need two dev_info at startup and shutdown since most
> > pci drivers won't print anything to system log when the driver is loaded or
> > unloaded ?
> 
> Definitely not needed, but the intention of this patch is to convert
> to dev_*().  There are some cleanups, but it's for removing redundant
> strings, so it's a bit different from changing the log level of the
> original code.  You can submit an additional patch to adjust the log
> levels more appropriately.
> 
sure , I will submit a separate patch for cleaning up these extra dev_info.

thanks
sudip
> 
> Takashi

      reply	other threads:[~2014-10-17  3:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-10  8:36 [PATCH v2 1/2] ALSA: au88x0: added reference of vortex_t Sudip Mukherjee
2014-10-10  8:36 ` [PATCH v2 2/2] ALSA: au88x0: pr_* replaced with dev_* Sudip Mukherjee
2014-10-11  7:20   ` Raymond Yau
2014-10-11  9:09     ` Sudip Mukherjee
2014-10-11  9:09       ` [alsa-devel] " Sudip Mukherjee
2014-10-11 10:48       ` Joe Perches
2014-10-11 10:48         ` [alsa-devel] " Joe Perches
2014-10-11 11:33         ` Sudip Mukherjee
2014-10-11 11:33           ` [alsa-devel] " Sudip Mukherjee
2014-10-11 15:32           ` Joe Perches
2014-10-11 18:10             ` Sudip Mukherjee
2014-10-11 18:22               ` Joe Perches
2014-10-11 18:22                 ` [alsa-devel] " Joe Perches
2014-10-11 18:25             ` Sudip Mukherjee
2014-10-16  3:04               ` Raymond Yau
2014-10-16 13:45                 ` [alsa-devel] " Takashi Iwai
2014-10-17  3:32                   ` Sudip Mukherjee [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=20141017033217.GA3554@sudip-PC \
    --to=sudipm.mukherjee@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=superquad.vortex2@gmail.com \
    --cc=tiwai@suse.de \
    /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.