From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Vincent Palatin <vpalatin@chromium.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Linux PCI <linux-pci@vger.kernel.org>,
Olof Johansson <olofj@chromium.org>,
Sameer Nanda <snanda@chromium.org>,
Ming Lei <tom.leiming@gmail.com>,
linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCH] PM / Runtime: make PCI traces quieter
Date: Mon, 5 Dec 2011 11:59:56 -0800 [thread overview]
Message-ID: <20111205115956.4d6920c1@jbarnes-desktop> (raw)
In-Reply-To: <1323114678-28750-1-git-send-email-vpalatin@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 605 bytes --]
On Mon, 5 Dec 2011 11:51:18 -0800
Vincent Palatin <vpalatin@chromium.org> wrote:
> When the runtime PM is activated on PCI, if a device switches state frequently
> (e.g. an EHCI controller with autosuspending USB devices connected)
> the PCI configuration traces might be very verbose in the kernel log.
> Let's guard those traces with DEBUG condition.
>
> Signed-off-by: Vincent Palatin <vpalatin@chromium.org>
> ---
Applied to linux-next, thanks. The latency timer message is gone now
though, so it didn't need to be fixed. :)
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2011-12-05 19:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP_ceTyXLO=mv1Ott=g3mG0y+Q+VUM3N8CA-Fqa-_=uj7LTbmw@mail.gmail.com>
[not found] ` <1316628308-32580-1-git-send-email-vpalatin@chromium.org>
[not found] ` <201109212029.38899.rjw@sisk.pl>
2011-11-28 19:15 ` [PATCH] PM / Runtime: make PCI traces quieter Vincent Palatin
2011-12-05 19:19 ` Jesse Barnes
2011-12-05 19:51 ` Vincent Palatin
2011-12-05 19:59 ` Jesse Barnes [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=20111205115956.4d6920c1@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=olofj@chromium.org \
--cc=rjw@sisk.pl \
--cc=snanda@chromium.org \
--cc=stern@rowland.harvard.edu \
--cc=tom.leiming@gmail.com \
--cc=vpalatin@chromium.org \
/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;
as well as URLs for NNTP newsgroup(s).