From: Thomas Gleixner <tglx@linutronix.de>
To: Jiang Liu <jiang.liu@linux.intel.com>
Cc: Alexander Holler <holler@ahsoftware.de>,
Mark Rustad <mark.d.rustad@intel.com>,
Alex Deucher <alexdeucher@gmail.com>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Tony Luck <tony.luck@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Bugfix] x86, irq: Fix a regression caused by commit b5dc8e6c21e7
Date: Mon, 17 Aug 2015 23:11:41 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1508172301350.3873@nanos> (raw)
In-Reply-To: <1439108128-18441-1-git-send-email-jiang.liu@linux.intel.com>
On Sun, 9 Aug 2015, Jiang Liu wrote:
> Alex Deucher, Mark Rustad and Alexander Holler reported a regression
> with the latest v4.2-rc4 kernel, which breaks some SATA controllers.
> With multi-MSI capable SATA controllers, only the first port works,
> all other ports times out when executing SATA commands. This regression
> bisects to 52f518a3a7c2 ("x86/MSI: Use hierarchical irqdomains to manage
> MSI interrupts"), but it's not the root cause, it just triggers a bug
> caused by b5dc8e6c21e7 ("x86/irq: Use hierarchical irqdomain to manage
> CPU interrupt vectors").
>
> With this patch applied, the affected SATA controllers work as expected.
This changelog including the subject line is horrible.
1) The subject line should describe the change in a short and precise form
x86/irq: Fix a regression caused by commit b5dc8e6c21e7
fits the short category, but completely fails to be precise. It's
not interesting for the subject line which commit caused the
problem and whether it's a regression or not. We want a to see a
proper description of the change itself.
2) The changelog should describe the bug itself.
... but it's not the root cause, it just triggers a bug caused by
b5dc8e6c21e7 ("x86/irq: Use hierarchical irqdomain to manage CPU
interrupt vectors").
does not tell what the actual bug in the code is.
3) The changelog should describe the solution.
With this patch applied, the affected SATA controllers work as
expected.
is describing the desired effect of the change, but not the change
itself.
Thanks,
tglx
next prev parent reply other threads:[~2015-08-17 21:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-09 8:15 Jiang Liu
2015-08-09 10:14 ` Alexander Holler
2015-08-09 14:11 ` Jiang Liu
2015-08-10 15:00 ` Alex Deucher
2015-08-11 1:06 ` Jiang Liu
2015-08-13 19:46 ` Alex Deucher
2015-08-13 20:15 ` Alex Deucher
2015-08-13 22:13 ` Alex Deucher
2015-08-25 4:03 ` Alex Deucher
2015-08-25 4:46 ` Jiang Liu
2015-08-10 16:47 ` Rustad, Mark D
2015-08-17 21:02 ` Alex Deucher
2015-08-18 12:53 ` Thomas Gleixner
2015-08-17 21:11 ` Thomas Gleixner [this message]
2015-08-18 15:20 ` [Bugfix] x86, irq: Fix an error in building CPU vector to IRQ number mapping for MSI Jiang Liu
2015-08-18 16:21 ` [tip:x86/urgent] x86/irq: Build correct vector mapping for multiple MSI interrupts tip-bot for Jiang Liu
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=alpine.DEB.2.11.1508172301350.3873@nanos \
--to=tglx@linutronix.de \
--cc=alexdeucher@gmail.com \
--cc=holler@ahsoftware.de \
--cc=hpa@zytor.com \
--cc=jiang.liu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.d.rustad@intel.com \
--cc=mingo@redhat.com \
--cc=tony.luck@intel.com \
--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
all inboxes | Powered by JetHome®