From: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
ath10k@lists.infradead.org,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: Re: [PATCH v2 0/4] ath10k: fixes
Date: Tue, 27 Aug 2013 00:59:56 -0700 [thread overview]
Message-ID: <20130827075438.GA29102@pogo> (raw)
In-Reply-To: <CA+BoTQ=zVAab8KV2TwYJ=+wG0N7M4-oo-TgaE2qpxJO33d3oZQ@mail.gmail.com>
On Tue, Aug 27, 2013 at 07:42:39AM +0200, Michal Kazior wrote:
> On 26 August 2013 22:20, Luis R. Rodriguez <mcgrof@do-not-panic.com> wrote:
> > On Mon, Aug 26, 2013 at 1:53 AM, Michal Kazior <michal.kazior@tieto.com> wrote:
> >> ath10k: fix issues on non-preemptible systems
> >
> > This patch looks like a stable candidate fix. Please annotate as such
> > if you confirm. Also, I reviewed other ath10k "fixes" and I see no
> > practice of propagating any patches to stable yet. Can you please
> > start doing that? If there were patches which are already merged
> > upstream that should be propagated to stable then they can be
> > submitted as stable candidate patches.
>
> Good point.
>
> If this patch is to be propagated to stable the patch(set) needs some
> adjustments to avoid conflicts. Right now the patch touches a place
> that was introduced with "ath10k: move htt rx processing to worker" so
> the offending patch hunk should be moved to that patch.
>
> Actually the "ath10k: make the workqueue multithreaded" could also be
> a candidate for stable as it fixes AP beaconing during heavy TX
> traffic. I should've mentioned that in the commit log.
>
> I'll resend an updated patchset later today.
That one doesn't seem like a stable fix, it does quite a big change.
Luis
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
<ath10k@lists.infradead.org>
Subject: Re: [PATCH v2 0/4] ath10k: fixes
Date: Tue, 27 Aug 2013 00:59:56 -0700 [thread overview]
Message-ID: <20130827075438.GA29102@pogo> (raw)
In-Reply-To: <CA+BoTQ=zVAab8KV2TwYJ=+wG0N7M4-oo-TgaE2qpxJO33d3oZQ@mail.gmail.com>
On Tue, Aug 27, 2013 at 07:42:39AM +0200, Michal Kazior wrote:
> On 26 August 2013 22:20, Luis R. Rodriguez <mcgrof@do-not-panic.com> wrote:
> > On Mon, Aug 26, 2013 at 1:53 AM, Michal Kazior <michal.kazior@tieto.com> wrote:
> >> ath10k: fix issues on non-preemptible systems
> >
> > This patch looks like a stable candidate fix. Please annotate as such
> > if you confirm. Also, I reviewed other ath10k "fixes" and I see no
> > practice of propagating any patches to stable yet. Can you please
> > start doing that? If there were patches which are already merged
> > upstream that should be propagated to stable then they can be
> > submitted as stable candidate patches.
>
> Good point.
>
> If this patch is to be propagated to stable the patch(set) needs some
> adjustments to avoid conflicts. Right now the patch touches a place
> that was introduced with "ath10k: move htt rx processing to worker" so
> the offending patch hunk should be moved to that patch.
>
> Actually the "ath10k: make the workqueue multithreaded" could also be
> a candidate for stable as it fixes AP beaconing during heavy TX
> traffic. I should've mentioned that in the commit log.
>
> I'll resend an updated patchset later today.
That one doesn't seem like a stable fix, it does quite a big change.
Luis
next prev parent reply other threads:[~2013-08-27 8:00 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 6:34 [PATCH 0/3] ath10k: fixes Michal Kazior
2013-08-21 6:34 ` Michal Kazior
2013-08-21 6:34 ` [PATCH 1/3] ath10k: make the workqueue multithreaded Michal Kazior
2013-08-21 6:34 ` Michal Kazior
2013-08-21 6:34 ` [PATCH 2/3] ath10k: move htt rx processing to worker Michal Kazior
2013-08-21 6:34 ` Michal Kazior
2013-08-21 6:34 ` [PATCH 3/3] ath10k: fix issues on non-preemptible systems Michal Kazior
2013-08-21 6:34 ` Michal Kazior
2013-08-22 10:05 ` [PATCH 0/3] ath10k: fixes Michal Kazior
2013-08-22 10:05 ` Michal Kazior
2013-08-26 8:53 ` [PATCH v2 0/4] " Michal Kazior
2013-08-26 8:53 ` Michal Kazior
2013-08-26 8:53 ` [PATCH v2 1/4] ath10k: synchronize tx/rx reporting to mac80211 Michal Kazior
2013-08-26 8:53 ` Michal Kazior
2013-08-28 4:23 ` Kalle Valo
2013-08-28 4:23 ` Kalle Valo
2013-08-28 10:54 ` Michal Kazior
2013-08-28 10:54 ` Michal Kazior
2013-08-28 11:04 ` Kalle Valo
2013-08-28 11:04 ` Kalle Valo
2013-08-26 8:53 ` [PATCH v2 2/4] ath10k: make the workqueue multithreaded Michal Kazior
2013-08-26 8:53 ` Michal Kazior
2013-08-26 8:53 ` [PATCH v2 3/4] ath10k: move htt rx processing to worker Michal Kazior
2013-08-26 8:53 ` Michal Kazior
2013-08-26 8:53 ` [PATCH v2 4/4] ath10k: fix issues on non-preemptible systems Michal Kazior
2013-08-26 8:53 ` Michal Kazior
2013-08-27 7:06 ` Kalle Valo
2013-08-27 7:06 ` Kalle Valo
2013-08-27 7:30 ` Michal Kazior
2013-08-27 7:30 ` Michal Kazior
2013-08-28 4:02 ` Kalle Valo
2013-08-28 4:02 ` Kalle Valo
2013-08-28 13:16 ` Michal Kazior
2013-08-28 13:16 ` Michal Kazior
2013-08-26 20:20 ` [PATCH v2 0/4] ath10k: fixes Luis R. Rodriguez
2013-08-26 20:20 ` Luis R. Rodriguez
2013-08-27 5:42 ` Michal Kazior
2013-08-27 5:42 ` Michal Kazior
2013-08-27 7:59 ` Luis R. Rodriguez [this message]
2013-08-27 7:59 ` Luis R. Rodriguez
2013-08-27 6:57 ` Kalle Valo
2013-08-27 6:57 ` Kalle Valo
2013-08-27 8:01 ` Luis R. Rodriguez
2013-08-27 8:01 ` Luis R. Rodriguez
2013-08-28 3:53 ` Kalle Valo
2013-08-28 3:53 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2013-08-08 8:16 [PATCH " Michal Kazior
2013-08-13 5:59 ` [PATCH v2 " Michal Kazior
2013-08-13 5:59 ` Michal Kazior
2013-08-14 15:02 ` Kalle Valo
2013-08-14 15:02 ` Kalle Valo
2013-07-18 6:33 [PATCH 0/3] " Michal Kazior
2013-07-22 12:13 ` [PATCH v2 0/4] " Michal Kazior
2013-07-22 12:13 ` Michal Kazior
2013-07-23 8:47 ` Kalle Valo
2013-07-23 8:47 ` Kalle Valo
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=20130827075438.GA29102@pogo \
--to=rodrigue@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=michal.kazior@tieto.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.