linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Curtin <ericcurtin17@gmail.com>
To: platform-driver-x86@vger.kernel.org
Cc: Kernel development list <linux-kernel@vger.kernel.org>,
	Darren Hart <dvhart@infradead.org>,
	Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
	ibm-acpi-devel@lists.sourceforge.net
Subject: [PATCH] Remove ambiguous logging for "Unsupported brightness interface"
Date: Wed, 27 Jan 2016 22:14:49 +0000	[thread overview]
Message-ID: <CANpvso5_jzOgRv25isy0x6HJcTgKP4dabSH-_a5fM-uihdAUYw@mail.gmail.com> (raw)

Message gets logged on machines that are well supported.

Signed-off-by: Eric Curtin <ericcurtin17@gmail.com>
---
 drivers/platform/x86/thinkpad_acpi.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/platform/x86/thinkpad_acpi.c
b/drivers/platform/x86/thinkpad_acpi.c
index a268a7a..4eb41aa 100644
--- a/drivers/platform/x86/thinkpad_acpi.c
+++ b/drivers/platform/x86/thinkpad_acpi.c
@@ -6661,7 +6661,6 @@ static void __init
tpacpi_detect_brightness_capabilities(void)
                pr_info("detected a 8-level brightness capable ThinkPad\n");
                break;
        default:
-               pr_info("Unsupported brightness interface\n");
                tp_features.bright_unkfw = 1;
                bright_maxlvl = b - 1;
        }
-- 
2.5.0

             reply	other threads:[~2016-01-27 22:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 22:14 Eric Curtin [this message]
2016-01-27 23:26 ` [PATCH] Remove ambiguous logging for "Unsupported brightness interface" Joe Perches
2016-01-28  0:36   ` Eric Curtin
2016-01-28  0:43     ` Joe Perches
2016-01-28  0:52       ` Eric Curtin
2016-01-30 12:20   ` Henrique de Moraes Holschuh
2016-01-30 16:55     ` Eric Curtin
2016-01-30 19:49       ` Henrique de Moraes Holschuh
2016-02-07 20:13       ` Darren Hart

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=CANpvso5_jzOgRv25isy0x6HJcTgKP4dabSH-_a5fM-uihdAUYw@mail.gmail.com \
    --to=ericcurtin17@gmail.com \
    --cc=dvhart@infradead.org \
    --cc=hmh@hmh.eng.br \
    --cc=ibm-acpi-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.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).