From: Thomas Gleixner <tglx@linutronix.de>
To: blinkin@email.it
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bug report for kernel v4.15-rc8+
Date: Tue, 10 Aug 2021 08:46:17 +0200 [thread overview]
Message-ID: <87tujxssp2.ffs@tglx> (raw)
In-Reply-To: <629765464.1655403.1628264743080.JavaMail.zimbra@email.it>
On Fri, Aug 06 2021 at 17:45, blinkin@email.it wrote:
> I'm not sure where and how to report it, the kernel I used for the
> tests is built from the opensuse tree but it looks like an upstream
> bug. Can you give me pointers on how to proceed from here? I can
> provide informations about the symptoms, the hardware config and the
> workaround but I know nothing about CPU/IRQ management in the linux
> kernel.
Detailed information about the problem would indeed be helpful.
Thanks,
tglx
next prev parent reply other threads:[~2021-08-10 6:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 15:45 Bug report for kernel v4.15-rc8+ blinkin
2021-08-10 6:46 ` Thomas Gleixner [this message]
2021-08-10 14:05 ` blinkin
2021-08-10 17:09 ` Thomas Gleixner
2021-08-11 13:51 ` blinkin
2021-08-11 14:20 ` Thomas Gleixner
2021-09-24 10:23 ` blinkin
-- strict thread matches above, loose matches on Subject: below --
2021-12-17 13:31 blinkin
2022-06-10 9:52 blinkin
2022-06-10 13:17 ` Rafael J. Wysocki
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=87tujxssp2.ffs@tglx \
--to=tglx@linutronix.de \
--cc=blinkin@email.it \
--cc=linux-kernel@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