All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Salah Triki <salah.triki@acm.org>
Cc: minchan@kernel.org, ngupta@vflare.org,
	linux-kernel@vger.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH] zram: Replace pr_* with dev_*
Date: Wed, 5 Aug 2015 08:57:05 +0900	[thread overview]
Message-ID: <20150804235705.GB4430@swordfish> (raw)
In-Reply-To: <20150804234225.GA4430@swordfish>

On (08/05/15 08:42), Sergey Senozhatsky wrote:
> what's the benefit?

and apart from that I don't understand why do you replace some
pr_info() with dev_warn(). f.e.

[..]
> >  		if (!zcomp_set_max_streams(zram->comp, num)) {
> > -			pr_info("Cannot change max compression streams\n");
> > +			dev_warn(dev, "Cannot change max compression streams to %d",
> > +				num);

			^^^

> >  			ret = -EINVAL;
> >  			goto out;
> >  		}
> > @@ -368,7 +369,7 @@ static ssize_t comp_algorithm_store(struct device *dev,
> >  	down_write(&zram->init_lock);
> >  	if (init_done(zram)) {
> >  		up_write(&zram->init_lock);
> > -		pr_info("Can't change algorithm for initialized device\n");
> > +		dev_warn(dev, "Can't change algorithm for initialized device");

		^^^

[..]



and sometimes you don't -- changing pr_info() to dev_info().

> >  	if (IS_ERR(comp)) {
> > -		pr_info("Cannot initialise %s compressing backend\n",
> > +		dev_info(dev, "Cannot initialise %s compressing backend",
> >  				zram->compressor);

		^^^


[..]

and then again...

> >  	down_write(&zram->init_lock);
> >  	if (init_done(zram)) {
> > -		pr_info("Cannot change disksize for initialized device\n");
> > +		dev_warn(dev, "Cannot change disksize for initialized device");

		^^^

[..]

	-ss

  reply	other threads:[~2015-08-04 23:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04 19:22 [PATCH] zram: Replace pr_* with dev_* Salah Triki
2015-08-04 23:42 ` Sergey Senozhatsky
2015-08-04 23:57   ` Sergey Senozhatsky [this message]
2015-08-05  1:16     ` Joe Perches

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=20150804235705.GB4430@swordfish \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=ngupta@vflare.org \
    --cc=salah.triki@acm.org \
    --cc=sergey.senozhatsky@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 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.