public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: greg@kroah•com (Greg KH)
To: linux-arm-kernel@lists•infradead.org
Subject: [RESEND PATCH] iio: adc: bcm_iproc_adc: swap primary and secondary isr handler's
Date: Tue, 16 May 2017 08:01:10 +0200	[thread overview]
Message-ID: <20170516060110.GA25722@kroah.com> (raw)
In-Reply-To: <1494913772-30904-1-git-send-email-raveendra.padasalagi@broadcom.com>

On Tue, May 16, 2017 at 11:19:32AM +0530, Raveendra Padasalagi wrote:
> The third argument of devm_request_threaded_irq() is the primary
> handler. It is called in hardirq context and checks whether the
> interrupt is relevant to the device. If the primary handler returns
> IRQ_WAKE_THREAD, the secondary handler (a.k.a. handler thread) is
> scheduled to run in process context.
> 
> bcm_iproc_adc.c uses the secondary handler as the primary one
> and the other way around. So this patch fixes the same, along with
> re-naming the secondary handler and primary handler names properly.
> 
> Tested on the BCM9583XX iProc SoC based boards.
> 
> Reported-by: Pavel Roskin <plroskin@gmail•com>
> Fixes: 4324c97ecedc("iio: Add driver for Broadcom iproc-static-adc")
> Signed-off-by: Raveendra Padasalagi <raveendra.padasalagi@broadcom•com>
> ---
>  drivers/iio/adc/bcm_iproc_adc.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)

<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read Documentation/stable_kernel_rules.txt
for how to do this properly.

</formletter>

  reply	other threads:[~2017-05-16  6:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16  5:49 [RESEND PATCH] iio: adc: bcm_iproc_adc: swap primary and secondary isr handler's Raveendra Padasalagi
2017-05-16  6:01 ` Greg KH [this message]
2017-05-16  6:08   ` Baruch Siach
2017-05-16  6:41     ` Greg KH

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=20170516060110.GA25722@kroah.com \
    --to=greg@kroah$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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