From: akpm@linux-foundation.org (Andrew Morton)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] sdhci-s3c: fix incorrect spinlock usage after merge
Date: Mon, 20 Sep 2010 18:29:12 -0700 [thread overview]
Message-ID: <20100920182912.a29ff3d1.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100921011711.GB5873@void.printf.net>
On Tue, 21 Sep 2010 02:17:11 +0100 Chris Ball <cjb@laptop.org> wrote:
> On Mon, Sep 20, 2010 at 03:03:42PM +0200, Marek Szyprowski wrote:
> > In the commit f522886e202a34a2191dd5d471b3c4d46410a9a0 a merge conflict
> > in the sdhci-s3c driver been fixed. However the fix used incorrect
> > spinlock operation - it cause a race with sdhci interrupt service. The
> > correct way to solve it is to use spin_lock_irqsave/irqrestore() calls.
>
> Thanks, applied to mmc-next with:
> Signed-off-by: Chris Ball <cjb@laptop.org>
>
> Andrew, not sure how best to get this upstream -- do you want to send
> this up to Linus (for -rc5) via your queue in -mm?
Ordinarily I'd expect you to send it to Linus.
I tend to merge important-looking bugfixes in my tree in case
maintainers lose them (happens regularly). I'll then start spamming
the maintainer with the patch. If the maintainer remains dead then I
might merge it myself, or I might tag it for -stable backporting and
try again in the next kernel.
If the maintainer can't be bothered setting up a pull request then he
can just send an acked-by and explicitly ask me to merge it up and
I'll then add it to my next approximately-weekly Linus patchbombing.
next prev parent reply other threads:[~2010-09-21 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 13:03 [PATCH] sdhci-s3c: fix incorrect spinlock usage after merge Marek Szyprowski
2010-09-21 1:17 ` Chris Ball
2010-09-21 1:29 ` Andrew Morton [this message]
2010-09-21 3:15 ` Chris Ball
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=20100920182912.a29ff3d1.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.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