From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: darkstar6262@gmail.com, linux-mmc@vger.kernel.org, tony@atomide.com
Subject: + omap-remove-bug_on-for-disabled-interrupts.patch added to -mm tree
Date: Wed, 02 Jun 2010 14:05:59 -0700 [thread overview]
Message-ID: <201006022105.o52L5xqC016900@imap1.linux-foundation.org> (raw)
The patch titled
omap: remove BUG_ON for disabled interrupts
has been added to the -mm tree. Its filename is
omap-remove-bug_on-for-disabled-interrupts.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: omap: remove BUG_ON for disabled interrupts
From: Cory Maccarrone <darkstar6262@gmail.com>
Remove a BUG_ON for when interrupts are disabled during an MMC request.
During boot, interrupts can be disabled when a request is made, causing
this bug to be triggered. In reality, there's no reason this should halt
the kernel, as the driver has proved reliable in spite of disabled
interrupts, and additionally, there's nothing in this code that would
require interrupts to be enabled.
Signed-off-by: Cory Maccarrone <darkstar6262@gmail.com>
Acked-by: Tony Lindgren <tony@atomide.com>
Cc: <linux-mmc@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/mmc/host/omap.c | 1 -
1 file changed, 1 deletion(-)
diff -puN drivers/mmc/host/omap.c~omap-remove-bug_on-for-disabled-interrupts drivers/mmc/host/omap.c
--- a/drivers/mmc/host/omap.c~omap-remove-bug_on-for-disabled-interrupts
+++ a/drivers/mmc/host/omap.c
@@ -1157,7 +1157,6 @@ static void mmc_omap_start_request(struc
mmc_omap_start_command(host, req->cmd);
if (host->dma_in_use)
omap_start_dma(host->dma_ch);
- BUG_ON(irqs_disabled());
}
static void mmc_omap_request(struct mmc_host *mmc, struct mmc_request *req)
_
Patches currently in -mm which might be from darkstar6262@gmail.com are
linux-next.patch
omap-remove-bug_on-for-disabled-interrupts.patch
reply other threads:[~2010-06-02 21:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201006022105.o52L5xqC016900@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=darkstar6262@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=tony@atomide.com \
/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