[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140311111156.GB27009@gmail.com>
Date: Tue, 11 Mar 2014 12:11:56 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Prarit Bhargava <prarit@...hat.com>
Cc: linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
Rui Wang <rui.y.wang@...el.com>,
Liu Ping Fan <kernelfans@...il.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@...achi.com>,
Lv Zheng <lv.zheng@...el.com>,
Seiji Aguchi <seiji.aguchi@....com>,
Yang Zhang <yang.z.zhang@...el.com>,
Andi Kleen <ak@...ux.intel.com>,
"Steven Rostedt (Red Hat)" <rostedt@...dmis.org>,
Li Fei <fei.li@...el.com>, gong.chen@...ux.intel.com
Subject: Re: [PATCH] x86, fix x86 fixup_irqs() error handling [v2]
* Prarit Bhargava <prarit@...hat.com> wrote:
> fixup_irqs() calls chip->set_irq_affinity which eventually calls
> __assign_irq_vector(). Errors are not propogated back from this function call
> and this results in silent irq relocation failures. This patch fixes this
> issue and prints out a warning if there is a relocation failure.
>
> [v2]: modified WARN to pr_crit and changed message
Please fix the changelog to conform to the standard changelog style:
- first describe the symptoms of the bug - how does a user notice?
- then describe how the code behaves today and how that is causing the bug
- and then only describe how it's fixed.
The first item is the most important one - yet it's missing from this
changelog.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists