public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Jaroslav Kysela <perex@perex.cz>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sound: pci: ctxfi: prink replacement
Date: Tue, 26 Aug 2014 12:33:28 +0200	[thread overview]
Message-ID: <s5hr4035ymf.wl-tiwai@suse.de> (raw)
In-Reply-To: <1409048004-19838-1-git-send-email-sudipm.mukherjee@gmail.com>

At Tue, 26 Aug 2014 15:43:24 +0530,
Sudip Mukherjee wrote:
> 
> printk replaced with corresponding pr_err and pr_alert
> 
> Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> ---
> 
> Initially started by copy-paste but as Takashi suggested it was done by a script.
> bash script is as follows :
> 
> OLD="printk(KERN_ERR \?"
> OLD1="printk(KERN_ALERT \?"
> NEW="pr_err("
> NEW1="pr_alert("
> TFILE="/tmp/out.tmp.$$"
> for f in *.c
> do
> sed "s/$OLD/$NEW/g" "$f" > $TFILE && mv $TFILE "$f"
> sed "s/$OLD1/$NEW1/g" "$f" > $TFILE && mv $TFILE "$f"
> done

All these can be a single call of sed :)

> this patch will generate a warning from checkpatch for an unnecessary space before new line and has not been fixed as this patch is only for printk replacement.

Better to put such information into the changelog.

Do you have the patch reformatting the broken lines, too?
If yes, I'll wait for it, as we should apply both such patches at
once.


Takashi

  reply	other threads:[~2014-08-26 10:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Re: [PATCH] sound: pci: ctxfi: ctatc.c: printk replacement>
2014-08-26 10:13 ` [PATCH] sound: pci: ctxfi: prink replacement Sudip Mukherjee
2014-08-26 10:33   ` Takashi Iwai [this message]
2014-08-26 11:51     ` 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=s5hr4035ymf.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.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