linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@googlemail.com>
To: Joe Perches <joe@perches.com>
Cc: Matthew Garrett <mjg@redhat.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	platform-driver-x86 <platform-driver-x86@vger.kernel.org>,
	ibm-acpi@hmh.eng.br
Subject: Re: linux-next: Tree for April 4 [BROKEN thinkpad_acpi]
Date: Mon, 4 Apr 2011 17:08:05 +0200	[thread overview]
Message-ID: <BANLkTik19DczZ9uoSQSvv_zpv5fpUR7kCw@mail.gmail.com> (raw)
In-Reply-To: <1301929346.1941.32.camel@Joe-Laptop>

On Mon, Apr 4, 2011 at 5:02 PM, Joe Perches <joe@perches.com> wrote:
> On Mon, 2011-04-04 at 16:44 +0200, Sedat Dilek wrote:
>> > I have tried with solution #2 as it partially restores old behaviour
>> > (patch is attached).
>
> Partially?  Please explain.
>
>

From [1] (platform-drivers-x86.git#linux-next):
...
 #ifdef CONFIG_THINKPAD_ACPI_DEBUG
 #define vdbg_printk dbg_printk
 static const char *str_supported(int is_supported);
 #else
-#define vdbg_printk(a_dbg_level, format, arg...) \
-       do { } while (0)
+#define vdbg_printk(a_dbg_level, format, arg...)       \
+       no_printk(format, ##arg)
 #endif
...

- Sedat -

[1] http://git.kernel.org/?p=linux/kernel/git/mjg59/platform-drivers-x86.git;a=blobdiff;f=drivers/platform/x86/thinkpad_acpi.c;h=d8f3e653e96d8d5ad2081e4794a8f70f852b20de;hp=a08561f5349ef038decaf8edcd73528f30f056a9;hb=2af915b1eda9a671973256540035f8a6da1d57b4;hpb=1ba77972006a7ad5fed0811aac3fed724e7c5a04

  reply	other threads:[~2011-04-04 15:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04  9:21 linux-next: Tree for April 4 [BROKEN thinkpad_acpi] Sedat Dilek
2011-04-04 12:22 ` Matthew Garrett
2011-04-04 12:49   ` Joe Perches
2011-04-04 13:00     ` Matthew Garrett
2011-04-04 13:44       ` Sedat Dilek
2011-04-04 14:44         ` Sedat Dilek
2011-04-04 15:02           ` Joe Perches
2011-04-04 15:08             ` Sedat Dilek [this message]
2011-04-04 15:13               ` Joe Perches
2011-04-05 12:27       ` Henrique de Moraes Holschuh

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=BANLkTik19DczZ9uoSQSvv_zpv5fpUR7kCw@mail.gmail.com \
    --to=sedat.dilek@googlemail.com \
    --cc=ibm-acpi@hmh.eng.br \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=sfr@canb.auug.org.au \
    /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).