From: Chris Ball <chris@printf.net>
To: Andrew Bresticker <abrestic@chromium.org>
Cc: John Tobias <john.tobias.ph@gmail.com>,
Philip Rakity <prakity@nvidia.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dong Aisheng <b29396@freescale.com>
Subject: Re: [PATCH] mmc: sdhci: fix possible scheduling while atomic
Date: Fri, 17 Jan 2014 23:40:47 +0000 [thread overview]
Message-ID: <86ha926utc.fsf@void.printf.net> (raw)
In-Reply-To: <CAL1qeaHr=VGJCH-ngMAskd8O8qa6u+0cuXodBNshdKBD10V27w@mail.gmail.com> (Andrew Bresticker's message of "Fri, 17 Jan 2014 15:16:42 -0800")
Hi, adding Aisheng,
On Fri, Jan 17 2014, Andrew Bresticker wrote:
> On Fri, Jan 17, 2014 at 3:11 PM, John Tobias <john.tobias.ph@gmail.com> wrote:
>> There's an existing patch for that...
>> http://www.spinics.net/lists/arm-kernel/msg296596.html
>
> Ah, I see. Looks like it has yet to be picked up...
The patches aren't quite identical -- Andrew's leaves the
disable_irq() call in and Aisheng's removes it. Which should I take?
Thanks,
- Chris.
--
Chris Ball <chris@printf.net> <http://printf.net/>
WARNING: multiple messages have this Message-ID (diff)
From: Chris Ball <chris@printf.net>
To: Andrew Bresticker <abrestic@chromium.org>
Cc: John Tobias <john.tobias.ph@gmail.com>,
Philip Rakity <prakity@nvidia.com>,
"linux-mmc\@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dong Aisheng <b29396@freescale.com>
Subject: Re: [PATCH] mmc: sdhci: fix possible scheduling while atomic
Date: Fri, 17 Jan 2014 23:40:47 +0000 [thread overview]
Message-ID: <86ha926utc.fsf@void.printf.net> (raw)
In-Reply-To: <CAL1qeaHr=VGJCH-ngMAskd8O8qa6u+0cuXodBNshdKBD10V27w@mail.gmail.com> (Andrew Bresticker's message of "Fri, 17 Jan 2014 15:16:42 -0800")
Hi, adding Aisheng,
On Fri, Jan 17 2014, Andrew Bresticker wrote:
> On Fri, Jan 17, 2014 at 3:11 PM, John Tobias <john.tobias.ph@gmail.com> wrote:
>> There's an existing patch for that...
>> http://www.spinics.net/lists/arm-kernel/msg296596.html
>
> Ah, I see. Looks like it has yet to be picked up...
The patches aren't quite identical -- Andrew's leaves the
disable_irq() call in and Aisheng's removes it. Which should I take?
Thanks,
- Chris.
--
Chris Ball <chris@printf.net> <http://printf.net/>
next prev parent reply other threads:[~2014-01-17 23:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 19:57 [PATCH] mmc: sdhci: fix possible scheduling while atomic Andrew Bresticker
2014-01-17 22:58 ` Philip Rakity
2014-01-17 23:10 ` Andrew Bresticker
2014-01-17 23:11 ` John Tobias
2014-01-17 23:16 ` Andrew Bresticker
2014-01-17 23:40 ` Chris Ball [this message]
2014-01-17 23:40 ` Chris Ball
2014-01-18 3:21 ` Andrew Bresticker
2014-01-18 3:40 ` Chris Ball
2014-01-18 3:40 ` Chris Ball
-- strict thread matches above, loose matches on Subject: below --
2014-01-20 9:51 Philip Rakity
2014-01-20 15:03 ` Philip Rakity
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=86ha926utc.fsf@void.printf.net \
--to=chris@printf.net \
--cc=abrestic@chromium.org \
--cc=b29396@freescale.com \
--cc=john.tobias.ph@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=prakity@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.