From: Luca Coelho <luca@coelho.fi>
To: Eliad Peller <eliad@wizery.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 12/12] wlcore: always register dummy hardirq
Date: Mon, 30 Sep 2013 19:48:00 +0300 [thread overview]
Message-ID: <1380559680.32539.1.camel@paschendale> (raw)
In-Reply-To: <CAB3XZEeer+NTKwWc5GkjZQdswSkPfsGhinvpcK2BbarqjCeA5A@mail.gmail.com>
On Wed, 2013-09-11 at 09:48 +0200, Eliad Peller wrote:
> On Tue, Sep 10, 2013 at 10:50 AM, Luca Coelho <luca@coelho.fi> wrote:
> > On Tue, 2013-09-03 at 17:34 +0300, Eliad Peller wrote:
> >> From: Arik Nemtsov <arik@wizery.com>
> >>
> >> This keeps the kernel happy when using edge-irqs and requesting a
> >> threaded irq.
> >>
> >> Signed-off-by: Arik Nemtsov <arik@wizery.com>
> >> Signed-off-by: Eliad Peller <eliad@wizery.com>
> >> ---
> >
> > Ouch, I think this is not going to fit at all with the DT patches I
> > sent.
> >
> this is quite minor patch (only making sure we always define hardirq
> when threaded_irq is used. i don't think it should conflict (at least
> logically) with DT patches...
It will. Just take a look at my DT patch series. Anyway, I'll apply
this for now and whoever (if ever) take over my DT series, will have to
make sure it still works. :P
--
Cheers,
Luca.
prev parent reply other threads:[~2013-09-30 16:53 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 14:33 [PATCH 01/12] wlcore: ROC on AP channel before auth reply Eliad Peller
2013-09-03 14:33 ` [PATCH 02/12] wlcore: add new plt power-mode: CHIP_AWAKE Eliad Peller
2013-09-10 6:33 ` Luca Coelho
2013-09-10 6:47 ` Arik Nemtsov
2013-09-10 6:56 ` Luca Coelho
2013-09-10 13:46 ` Eliad Peller
2013-09-10 19:16 ` Luca Coelho
2013-09-03 14:33 ` [PATCH 03/12] wlcore: disable elp sleep while in plt mode Eliad Peller
2013-09-10 6:34 ` Luca Coelho
2013-09-10 14:04 ` Eliad Peller
2013-09-10 19:24 ` Luca Coelho
2013-09-11 8:03 ` Eliad Peller
2013-09-03 14:34 ` [PATCH 04/12] wlcore: re-enable idle handling Eliad Peller
2013-09-03 14:34 ` [PATCH 05/12] wl18xx: increase the number of allowed BA sessions Eliad Peller
2013-09-10 6:39 ` Luca Coelho
2013-09-10 14:11 ` Eliad Peller
2013-09-03 14:34 ` [PATCH 06/12] wlcore: send EAPOL frames with voice priority Eliad Peller
2013-09-10 6:47 ` Luca Coelho
2013-09-10 9:11 ` Arik Nemtsov
2013-09-10 9:15 ` Luca Coelho
2013-09-10 14:15 ` Eliad Peller
2013-09-10 15:31 ` Ben Greear
2013-09-10 19:26 ` Luca Coelho
2013-09-03 14:34 ` [PATCH 07/12] wlcore: cleanup scan debug prints Eliad Peller
2013-09-10 7:19 ` Luca Coelho
2013-09-11 7:19 ` Eliad Peller
2013-09-03 14:34 ` [PATCH 08/12] wlcore: fix unsafe dereference of the wlvif Eliad Peller
2013-09-03 14:34 ` [PATCH 09/12] wlcore: fix regulatory domain bit translation Eliad Peller
2013-09-10 7:39 ` Luca Coelho
2013-09-10 14:51 ` Eliad Peller
2013-09-10 19:41 ` Luca Coelho
2013-09-03 14:34 ` [PATCH 10/12] wl18xx: fix boot process in high temperature environment Eliad Peller
2013-09-03 14:34 ` [PATCH 11/12] wl18xx: print new RDL versions during boot Eliad Peller
2013-09-10 7:47 ` Luca Coelho
2013-09-11 8:10 ` Eliad Peller
2013-09-03 14:34 ` [PATCH 12/12] wlcore: always register dummy hardirq Eliad Peller
2013-09-10 7:50 ` Luca Coelho
2013-09-11 7:48 ` Eliad Peller
2013-09-30 16:48 ` Luca Coelho [this message]
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=1380559680.32539.1.camel@paschendale \
--to=luca@coelho.fi \
--cc=eliad@wizery.com \
--cc=linux-wireless@vger.kernel.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