All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Wang Qize <wang_qize@venustech.com.cn>
Subject: Re: ACPI: sbshc: remove raw pointer from printk message
Date: Sat, 20 Jan 2018 08:36:13 +0100	[thread overview]
Message-ID: <20180120073613.GB18663@kroah.com> (raw)
In-Reply-To: <CAJZ5v0jh7sUje5RcEJVT_bLM9u=9z0pbPBEWy=4k-tfKfKO-SQ@mail.gmail.com>

On Sat, Jan 20, 2018 at 12:53:39AM +0100, Rafael J. Wysocki wrote:
> On Fri, Jan 19, 2018 at 10:06 AM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > There's no need to be printing a raw kernel pointer to the kernel log at
> > every boot.  So just remove it, and change the whole message to use the
> > correct dev_info() call at the same time.
> >
> > Reported-by: Wang Qize <wang_qize@venustech.com.cn>
> > Cc: stable <stable@vger.kernel.org>
> 
> I will remember this one. ;-)
> 
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> 
> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

Does that mean you want me to take this through my tree?  Or is there an
acpi tree it will go through?

thanks,

greg k-h

  reply	other threads:[~2018-01-20  7:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19  9:06 ACPI: sbshc: remove raw pointer from printk message Greg Kroah-Hartman
2018-01-19 23:53 ` Rafael J. Wysocki
2018-01-20  7:36   ` Greg Kroah-Hartman [this message]
2018-01-20  8:03     ` Rafael J. Wysocki
2018-01-20  8:16       ` Greg Kroah-Hartman
2018-01-22  3:19         ` wang_qize
2018-01-22  7:18           ` Greg Kroah-Hartman

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=20180120073613.GB18663@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=wang_qize@venustech.com.cn \
    /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.