alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ALSA: korg1212: cleanup of printk
Date: Wed, 26 Nov 2014 10:27:05 -0800	[thread overview]
Message-ID: <1417026425.19695.10.camel@perches.com> (raw)
In-Reply-To: <20141126104912.GA1085@sudip-PC>

On Wed, 2014-11-26 at 16:19 +0530, Sudip Mukherjee wrote:
> On Tue, Nov 25, 2014 at 10:59:25AM -0800, Joe Perches wrote:
> > On Tue, 2014-11-25 at 11:51 +0530, Sudip Mukherjee wrote:
> > > problems with this way:
> > > 1) macro name is little misleading - macro says printk, but we are using dev_dbg
> > > 2) if some one later wants to add something to this file, and doesnot want to use the variable name korg1212 in his function.
> > > 
> > > any suggestions ?
> > 
> > Some code is so old and unlikely to be ever used
> > again, it may be better to move it to an "ancient
> > and crufty" folder and forget about it.
> > 
> > This may be one of those.
> > 
> > If the debugging was written in a more current style,
> > it might look like this: (with various format/argument
> > mismatches fixed, formatting changes, etc)
> 
> ok. and can't we delete some of the messages like "DSP download is
> complete." and then printing the statename. there are lots of messages
> like that which is just printing the function name and the
> statename ..

Dunno.  Maybe somebody cares about the state of
the dsp download, but I doubt it as I suspect
the hardware isn't used much.

> and, even if i modify it a little and send it, most of the work has
> been done by you. so how do i send the patch in your name or add your
> name in the patch ? I have not done anything so my name should not be
> there.

<shrug> you started it.

I spend a couple minutes running a couple scripts.

I don't have the hardware, I've never looked at
that code before, do what you think appropriate.

      reply	other threads:[~2014-11-26 18:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-23  8:10 [PATCH v2] ALSA: korg1212: cleanup of printk Sudip Mukherjee
2014-11-24 17:08 ` Takashi Iwai
2014-11-24 17:25   ` Joe Perches
2014-11-25  6:21     ` Sudip Mukherjee
2014-11-25 18:59       ` Joe Perches
2014-11-26 10:49         ` Sudip Mukherjee
2014-11-26 18:27           ` Joe Perches [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=1417026425.19695.10.camel@perches.com \
    --to=joe@perches.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=sudipm.mukherjee@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 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).