public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Eli Cohen <eli@mellanox.com>, Steve Wise <swise@chelsio.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Sean Hefty <sean.hefty@intel.com>,
	Hal Rosenstock <hal.rosenstock@gmail.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: [resend/refresh PATCH] infiniband: Remove duplicated KERN_<LEVEL> from pr_<level> uses
Date: Tue, 12 May 2015 15:53:07 -0400	[thread overview]
Message-ID: <1431460387.43876.75.camel@redhat.com> (raw)
In-Reply-To: <1431125887.22450.35.camel@perches.com>

[-- Attachment #1: Type: text/plain, Size: 674 bytes --]

On Fri, 2015-05-08 at 15:58 -0700, Joe Perches wrote:
> These KERN_<LEVEL> uses are unnecessary with pr_<level> and cause
> bad logging output so remove them.
> 
> Signed-off-by: Joe Perches <joe@perches.com>
> Acked-by: Steve Wise <swise@opengridcomputing.com>
> ---
> 
> Originally sent Jan 5,  This is refreshed against -next.
> 
> Now sent to the new maintainer too.
> 
> Rasmus Villemoes sent a similar patchset a month later.
> https://lkml.org/lkml/2015/2/5/724
> 
> Rasmus' had an additional change that's useful.
> I don't care which is applied.

Applied, thanks.


-- 
Doug Ledford <dledford@redhat.com>
              GPG KeyID: 0E572FDD


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-05-12 19:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 22:58 [resend/refresh PATCH] infiniband: Remove duplicated KERN_<LEVEL> from pr_<level> uses Joe Perches
2015-05-12 19:53 ` Doug Ledford [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=1431460387.43876.75.camel@redhat.com \
    --to=dledford@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=eli@mellanox.com \
    --cc=hal.rosenstock@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=sean.hefty@intel.com \
    --cc=swise@chelsio.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