From: ulf.hansson@stericsson.com (Ulf Hansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmc: mmci: Do not release spinlock in request_end
Date: Fri, 14 Oct 2011 10:22:09 +0200 [thread overview]
Message-ID: <4E97F131.6090406@stericsson.com> (raw)
In-Reply-To: <20111014080318.GR21648@n2100.arm.linux.org.uk>
>> If you do not update your tree how shall we be able to
>> continue with integration of new patches that depends on mmc patches
>> from "next"?
>
> That's what I'm saying - I can't take the patch as it introduces bugs
> if I do. It's better to either wait until after the next merge window,
> or we have to sort out merging it via the mmc tree instead.
>
Thanks, now I really get the problem! :-)
From mmci host driver perspective this will then be kind of complicated
since it sometimes will depend on the patches on the mmc "framework".
Now we have the spinlock patch, but I believe this will happen soon
again. So how can we handle to merge it via mmc tree instead? Will you
be able to "Ack" patches for mmci so Chris Ball can merge them for the
mmc tree instead? Of course I only mean patches that really has a
dependency, the rest can be handled as is I believe.
BR
Uffe
next prev parent reply other threads:[~2011-10-14 8:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 14:06 [PATCH] mmc: mmci: Do not release spinlock in request_end Ulf Hansson
2011-10-12 9:41 ` Linus Walleij
2011-10-12 10:33 ` Adrian Hunter
2011-10-13 14:29 ` Russell King - ARM Linux
2011-10-13 15:59 ` Jon Medhurst (Tixy)
2011-10-14 7:37 ` Ulf Hansson
2011-10-14 7:42 ` Russell King - ARM Linux
2011-10-14 7:51 ` Ulf Hansson
2011-10-14 8:03 ` Russell King - ARM Linux
2011-10-14 8:22 ` Ulf Hansson [this message]
2011-10-16 20:34 ` Linus Walleij
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=4E97F131.6090406@stericsson.com \
--to=ulf.hansson@stericsson.com \
--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;
as well as URLs for NNTP newsgroup(s).