From: Dmitry Ilvokhin <d@ilvokhin.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH] x86/irq: Optimize interrupts decimals printing
Date: Wed, 15 Oct 2025 09:36:09 +0000 [thread overview]
Message-ID: <aO9rCaHLaXd-iJmi@shell.ilvokhin.com> (raw)
In-Reply-To: <aNrBL0Pi6kYXHGxQ@shell.ilvokhin.com>
Hello everyone,
Just want to follow up on this patch. Does this change looks reasonable
to you? I would appreciate any feedback, and thank you in advance for
the time spent reviewing it.
Best regards,
Dmitry
next prev parent reply other threads:[~2025-10-15 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 17:26 [PATCH] x86/irq: Optimize interrupts decimals printing Dmitry Ilvokhin
2025-10-15 9:36 ` Dmitry Ilvokhin [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-29 17:21 Dmitry Ilvokhin
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=aO9rCaHLaXd-iJmi@shell.ilvokhin.com \
--to=d@ilvokhin.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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