From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [PATCH] x86: io-apic - do not use KERN_DEBUG marker too much
Date: Sat, 13 Sep 2008 00:18:48 +0400 [thread overview]
Message-ID: <20080912201848.GB8410@lenovo> (raw)
In-Reply-To: <86802c440809121257s23e5193aqb7939fdc94473c9d@mail.gmail.com>
[Yinghai Lu - Fri, Sep 12, 2008 at 12:57:21PM -0700]
...
| > IOAPIC[0]: Set routing entry (8-14 -> 0x3e -> IRQ 14 Mode:0 Active:0)
| > 0 add_pin_to_irq: irq 15 --> apic 0 pin 15
| > IOAPIC[0]: Set routing entry (8-15 -> 0x3f -> IRQ 15 Mode:0 Active:0)
| > 8-16 8-17 8-18 8-19 8-20 8-21 8-22 8-23 (apicid-pin) not connected
| > 9-0 9-1 9-2 9-3 9-4 9-5 9-6 9-7 9-8 9-9 9-10 9-11 9-12 9-13 9-14 9-15
| > 9-16 9-17 9-18 9-19 9-20 9-21 9-22 9-23 (apicid-pin) not connected
| >
|
| only first one not connected at first, and ...
|
| why not just revert those two patches?
|
| YH
|
ok, convinced - Ingo, could you drop them please?
(yes, I've missed one new-line printing, sorry -
but quite frankly - it reveals another problem -
printing between other printing - which means
ideally it would be to _have_ temporary buffer apart
from printk buffer. So we have - either adding additional
new line printout 'cause of printing inbetween or our
own buffer to be able to print in nice-fasion. Anyway
I'm fine to just revert these attempts made. And thanks
Yinghai for comments and testing!)
- Cyrill -
next prev parent reply other threads:[~2008-09-12 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 15:38 [PATCH] x86: io-apic - do not use KERN_DEBUG marker too much Cyrill Gorcunov
2008-09-12 19:55 ` Yinghai Lu
2008-09-12 19:57 ` Yinghai Lu
2008-09-12 20:18 ` Cyrill Gorcunov [this message]
2008-09-13 0:40 ` Maciej W. Rozycki
2008-09-13 9:11 ` Cyrill Gorcunov
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=20080912201848.GB8410@lenovo \
--to=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=yhlu.kernel@gmail.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