From: Chris Ball <cjb@laptop.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-mmc@vger.kernel.org, linux-sh@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH/RFC] mmc: sh-mmcif: simplify IRQ processing
Date: Mon, 14 Jan 2013 14:17:44 -0500 [thread overview]
Message-ID: <87hamjtvzb.fsf@laptop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1212121540250.10522@axis700.grange> (Guennadi Liakhovetski's message of "Wed, 12 Dec 2012 15:45:14 +0100 (CET)")
Hi Guennadi,
On Wed, Dec 12 2012, Guennadi Liakhovetski wrote:
> The classical way to process IRQs is read out the status, ack all triggered
> IRQs, possibly mask them, then process them. Follow this simple procesure
> instead of the current complex custom algorithm.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> ---
>
> Hi Chris
>
> Attention: this patch is __NOT__ for 3.8, please, let it simmer in -next
> until 3.9. It modifies the driver's interrupt handling significantly, so,
> we want to have it tested over a longer period.
Sorry for the delay, this is in mmc-next now.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
WARNING: multiple messages have this Message-ID (diff)
From: Chris Ball <cjb@laptop.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-mmc@vger.kernel.org, linux-sh@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH/RFC] mmc: sh-mmcif: simplify IRQ processing
Date: Mon, 14 Jan 2013 19:17:44 +0000 [thread overview]
Message-ID: <87hamjtvzb.fsf@laptop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1212121540250.10522@axis700.grange> (Guennadi Liakhovetski's message of "Wed, 12 Dec 2012 15:45:14 +0100 (CET)")
Hi Guennadi,
On Wed, Dec 12 2012, Guennadi Liakhovetski wrote:
> The classical way to process IRQs is read out the status, ack all triggered
> IRQs, possibly mask them, then process them. Follow this simple procesure
> instead of the current complex custom algorithm.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> ---
>
> Hi Chris
>
> Attention: this patch is __NOT__ for 3.8, please, let it simmer in -next
> until 3.9. It modifies the driver's interrupt handling significantly, so,
> we want to have it tested over a longer period.
Sorry for the delay, this is in mmc-next now.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2013-01-14 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 14:45 [PATCH/RFC] mmc: sh-mmcif: simplify IRQ processing Guennadi Liakhovetski
2012-12-12 14:45 ` Guennadi Liakhovetski
2013-01-14 19:17 ` Chris Ball [this message]
2013-01-14 19:17 ` 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=87hamjtvzb.fsf@laptop.org \
--to=cjb@laptop.org \
--cc=g.liakhovetski@gmx.de \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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.