From: Takashi Iwai <tiwai@suse.de>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Jaroslav Kysela <perex@perex.cz>,
linuxppc-dev@lists.ozlabs.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sound: aoa: printk replacement
Date: Wed, 10 Sep 2014 16:43:03 +0200 [thread overview]
Message-ID: <s5hk35b4juw.wl-tiwai@suse.de> (raw)
In-Reply-To: <20140910143204.GA30695@sudip-PC>
At Wed, 10 Sep 2014 20:02:04 +0530,
Sudip Mukherjee wrote:
>
> On Wed, Sep 10, 2014 at 03:57:04PM +0200, Johannes Berg wrote:
> > On Wed, 2014-09-10 at 19:21 +0530, Sudip Mukherjee wrote:
> > > as pr_* macros are more preffered over printk, so printk replaced
> > > with corresponding pr_* macros.
> >
> > Are you simply running checkpatch on every file and decided to do
> > something about it? :)
> >
> i am running checkpatch on the patch generated. if i am doing checkpatch
> cleanups then that i do it only in the staging.
> only exception : printk .. :)
>
> > I'll let Takashi decide whether to take this or not as I no longer care
> > about this code, but IMHO this changes is completely pointless since you
> > don't also clean up the code to have a common prefix with #define pr_fmt
> > and then clean up the callers etc.
> >
> i mentioned in the comment that in a future patch we can have pr_fmt,
> it was not done in this patch since the changes for this patch is
> generated by a script and not manually.
> if Takashi accepts this then the next patch will have pr_fmt.
If you're going to work on it, please give a patch series and let me
merge once. There is no good merit to merge a half-baked piece by
piece.
Regarding the changes you've made: so far, I've merged two such
patches just because it's a good exercise for newbies. You've played
it and experienced it enough. So it's time to go up to a higher
stage, more "real" fixes.
For example, if you are still interested in printk stuff, try to
change the calls to dev_err() and co. Of course, this needs more
understanding of the code you'll handle, which object is passed for
which messages.
thanks,
Takashi
next prev parent reply other threads:[~2014-09-10 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 13:51 Sudip Mukherjee
2014-09-10 13:57 ` Johannes Berg
2014-09-10 14:32 ` Sudip Mukherjee
2014-09-10 14:43 ` Takashi Iwai [this message]
2014-09-10 15:07 ` Sudip Mukherjee
2014-09-10 15:38 ` Takashi Iwai
2014-09-10 17:14 ` Sudip Mukherjee
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=s5hk35b4juw.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=perex@perex.cz \
--cc=sudipm.mukherjee@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®