From: Kalle Valo <kvalo@qca.qualcomm.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Michal Kazior <michal.kazior@tieto.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 09:57:22 +0300 [thread overview]
Message-ID: <87mwo3mxil.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: CAB=NE6X=P2hTnOC8xqFwb=-32-hBgx=ndq3KHoUG83KptKv0vA@mail.gmail.com
"Luis R. Rodriguez" <mcgrof@do-not-panic.com> writes:
> 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.
I disagree. The point of linux-stable is _not_ that we send all possible
fixes to stable. Instead we should send fixes only which really matter
to users and for which we have received bug reports. I haven't yet seen
any fix for ath10k which should be a candidate for stable releases.
If we start sending all ath10k fixes to stable it's just extra churn for
both Greg and people working on ath10k.
--
Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Michal Kazior <michal.kazior@tieto.com>,
ath10k@lists.infradead.org
Subject: Re: [PATCH v2 0/4] ath10k: fixes
Date: Tue, 27 Aug 2013 09:57:22 +0300 [thread overview]
Message-ID: <87mwo3mxil.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: CAB=NE6X=P2hTnOC8xqFwb=-32-hBgx=ndq3KHoUG83KptKv0vA@mail.gmail.com
"Luis R. Rodriguez" <mcgrof@do-not-panic.com> writes:
> 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.
I disagree. The point of linux-stable is _not_ that we send all possible
fixes to stable. Instead we should send fixes only which really matter
to users and for which we have received bug reports. I haven't yet seen
any fix for ath10k which should be a candidate for stable releases.
If we start sending all ath10k fixes to stable it's just extra churn for
both Greg and people working on ath10k.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2013-08-27 6:57 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
2013-08-27 7:59 ` Luis R. Rodriguez
2013-08-27 6:57 ` Kalle Valo [this message]
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=87mwo3mxil.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@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.