From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch] sparc64: enable IRQs on error paths
Date: Fri, 25 Nov 2016 12:32:28 +0000 [thread overview]
Message-ID: <20161125123228.GA7578@oracle.com> (raw)
In-Reply-To: <20161125111054.GE5938@mwanda>
On (11/25/16 14:12), Dan Carpenter wrote:
> There are several error paths where we should enable IRQs but we don't.
>
> Fixes: bb620c3d3925 ("sparc: Make sparc64 use scalable lib/iommu-common.c functions")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
I dont have any problem with the fix, but the commit id flagged in
"Fixes" is inaccurate- this problem pre-existed before bb620c3d3925.
I think 6a32fd4d is the commit that this Fixes.
--Sowmini
next prev parent reply other threads:[~2016-11-25 12:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 11:12 [patch] sparc64: enable IRQs on error paths Dan Carpenter
2016-11-25 12:32 ` Sowmini Varadhan [this message]
2016-11-25 13:01 ` Dan Carpenter
2016-11-25 13:11 ` Sowmini Varadhan
2016-11-25 13:46 ` Dan Carpenter
2016-11-25 13:57 ` Sowmini Varadhan
2016-11-25 20:45 ` Sam Ravnborg
2016-11-25 21:06 ` tndave
2016-11-25 21:11 ` Dan Carpenter
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=20161125123228.GA7578@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=kernel-janitors@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;
as well as URLs for NNTP newsgroup(s).