All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Joe Perches <joe@perches.com>
Cc: Benjamin Romer <benjamin.romer@unisys.com>,
	David Kershner <david.kershner@unisys.com>,
	devel@driverdev.osuosl.org, sparmaintainer@unisys.com,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: unisys: Convert direct LOGERR uses to pr_err
Date: Sat, 10 Jan 2015 20:13:19 -0800	[thread overview]
Message-ID: <20150111041319.GB22334@kroah.com> (raw)
In-Reply-To: <1420945742.16787.12.camel@perches.com>

On Sat, Jan 10, 2015 at 07:09:02PM -0800, Joe Perches wrote:
> Use the normal logging facility instead of a new macro.
> 
> Miscellanea:
> 
> o Realign arguments
> o Remove unnecessary alloc error messages as alloc failures
>   already emits a generic OOM message with a dump_stack
> o Add missing newlines to these messages to avoid interleaving
> o Spelling/typo fixes in those messages
> 
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
>  drivers/staging/unisys/include/uisutils.h          |   4 +-
>  drivers/staging/unisys/uislib/uislib.c             | 169 ++++++++++-----------
>  drivers/staging/unisys/uislib/uisqueue.c           |   4 +-
>  drivers/staging/unisys/uislib/uisthread.c          |   4 +-
>  drivers/staging/unisys/uislib/uisutils.c           |  34 ++---
>  drivers/staging/unisys/virthba/virthba.c           | 119 +++++++--------
>  drivers/staging/unisys/virtpci/virtpci.c           |  71 +++++----
>  drivers/staging/unisys/visorchipset/file.c         |   2 +-
>  .../unisys/visorchipset/visorchipset_main.c        | 159 ++++++++++---------
>  9 files changed, 276 insertions(+), 290 deletions(-)
> 
> diff --git a/drivers/staging/unisys/include/uisutils.h b/drivers/staging/unisys/include/uisutils.h
> index 7414220..f937892 100644
> --- a/drivers/staging/unisys/include/uisutils.h
> +++ b/drivers/staging/unisys/include/uisutils.h
> @@ -206,10 +206,10 @@ wait_for_valid_guid(uuid_le __iomem *guid)
>  			      (void __iomem *)guid, sizeof(uuid_le));
>  		if (uuid_le_cmp(tmpguid, NULL_UUID_LE) != 0)
>  			break;
> -		LOGERR("Waiting for non-0 GUID (why???)...\n");
> +		pr_err("Waiting for non-0 GUID (why???)...\n");

I rejected the other patch that did much this same thing, almost all of
these should be converted to use dev_* calls instead of pr_* calls, as
this is a driver, and drivers should always have access to a struct
device.  If not, they need to be fixed.

thanks,

greg k-h

  reply	other threads:[~2015-01-11  4:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-11  3:09 [PATCH] staging: unisys: Convert direct LOGERR uses to pr_err Joe Perches
2015-01-11  4:13 ` Greg Kroah-Hartman [this message]
2015-01-11  4:55   ` Joe Perches
2015-01-11  5:24     ` Greg Kroah-Hartman
2015-01-11  5:32       ` Joe Perches
2015-01-11  5:51         ` Greg Kroah-Hartman
2015-01-11 16:57         ` Greg Kroah-Hartman
2015-01-11 17:04           ` 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=20150111041319.GB22334@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=benjamin.romer@unisys.com \
    --cc=david.kershner@unisys.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparmaintainer@unisys.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.