From: Wim Osterholt <wim@djo.tudelft.nl>
To: okaya@codeaurora.org
Cc: Bjorn Helgaas <helgaas@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
perex@perex.cz, linux-pci@vger.kernel.org,
Takashi Iwai <tiwai@suse.com>,
linux-pci-owner@vger.kernel.org,
Wim Osterholt <wim@djo.tudelft.nl>
Subject: Re: kernel-4.7 bug in Intel sound and/or ACPI
Date: Thu, 23 Jun 2016 16:12:35 +0200 [thread overview]
Message-ID: <20160623141234.GA14662@djo.tudelft.nl> (raw)
In-Reply-To: <72eb7b76d449f906d9b2b1bb15d995bf@codeaurora.org>
On Wed, Jun 22, 2016 at 11:54:39PM -0400, okaya@codeaurora.org wrote:
> On 2016-06-21 18:13, Wim Osterholt wrote:
> >>
> >> pr_info("%s:%d irq = %d penalty = %d\n", __func__, __LINE__, irq,
> >> penalty);
> >>
> >
> > This produced some 60 lines extra....
>
> Thanks, let's go back to 4.6 and add a very similar printf to every
> single place where the array is modified and also right before the
> enabled message.
>
I don't get this right.
Assuming that you're still talking about the same file, I find a few
instances of 'enabled', most of them in if-statements and one where it might
be set, so it looks. However, that's already in a printk statement.
I don't know about arrays and even less where these are set. Even worse, I
don't know what to put in a 'similar' line if you don't mean 'exactly the
same'.
So please state file and line numbers and the line to be inserted.
Groeten, Wim.
----- wim@djo.tudelft.nl -----
next prev parent reply other threads:[~2016-06-23 14:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 0:35 kernel-4.7 bug in Intel sound and/or ACPI Wim Osterholt
2016-06-20 1:02 ` Rafael J. Wysocki
2016-06-20 21:25 ` Bjorn Helgaas
2016-06-20 22:25 ` Sinan Kaya
2016-06-21 12:47 ` Wim Osterholt
2016-06-21 13:40 ` Sinan Kaya
2016-06-21 22:13 ` Wim Osterholt
2016-06-23 3:54 ` okaya
2016-06-23 14:12 ` Wim Osterholt [this message]
2016-06-23 14:55 ` Sinan Kaya
2016-06-23 15:45 ` Sinan Kaya
2016-06-23 16:21 ` Bjorn Helgaas
2016-06-23 17:05 ` Alex Williamson
2016-06-23 23:25 ` Wim Osterholt
2016-06-24 6:09 ` Sinan Kaya
2016-06-25 1:39 ` Wim Osterholt
2016-06-25 8:51 ` okaya
2016-06-27 6:27 ` Wim Osterholt
2016-06-27 8:22 ` okaya
2016-06-27 13:04 ` Wim Osterholt
2016-06-27 21:05 ` okaya
2016-06-29 8:34 ` Sinan Kaya
2016-06-30 2:30 ` Wim Osterholt
2016-06-30 9:43 ` okaya
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=20160623141234.GA14662@djo.tudelft.nl \
--to=wim@djo.tudelft.nl \
--cc=helgaas@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci-owner@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=okaya@codeaurora.org \
--cc=perex@perex.cz \
--cc=rjw@rjwysocki.net \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).