From: Kalle Valo <kvalo@qca.qualcomm.com>
To: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.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: Wed, 28 Aug 2013 06:53:53 +0300 [thread overview]
Message-ID: <87bo4ilbce.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20130827080144.GB29102@pogo> (Luis R. Rodriguez's message of "Tue, 27 Aug 2013 01:01:44 -0700")
"Luis R. Rodriguez" <rodrigue@qca.qualcomm.com> writes:
>> 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.
>
> You don't need to wait for an issue to happen to consider it serious,
> the description of the symptoms seem pretty bad to me, but its your
> call in the end.
>
>> If we start sending all ath10k fixes to stable it's just extra churn for
>> both Greg and people working on ath10k.
>
> I'm not asking for anything that has the word "fix" to be sent, I'm
> asking them to be reviewed for stable consideration.
I think a good rule is that we should send fixes to stable only if a
user (!= developer) has reported the problem.
--
Kalle Valo
next prev parent reply other threads:[~2013-08-28 3:53 UTC|newest]
Thread overview: 27+ 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 ` [PATCH 1/3] ath10k: make the workqueue multithreaded Michal Kazior
2013-08-21 6:34 ` [PATCH 2/3] ath10k: move htt rx processing to worker Michal Kazior
2013-08-21 6:34 ` [PATCH 3/3] ath10k: fix issues on non-preemptible systems Michal Kazior
2013-08-22 10:05 ` [PATCH 0/3] ath10k: fixes Michal Kazior
2013-08-26 8:53 ` [PATCH v2 0/4] " Michal Kazior
2013-08-26 8:53 ` [PATCH v2 1/4] ath10k: synchronize tx/rx reporting to mac80211 Michal Kazior
2013-08-28 4:23 ` Kalle Valo
2013-08-28 10:54 ` Michal Kazior
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 ` [PATCH v2 3/4] ath10k: move htt rx processing to worker Michal Kazior
2013-08-26 8:53 ` [PATCH v2 4/4] ath10k: fix issues on non-preemptible systems Michal Kazior
2013-08-27 7:06 ` Kalle Valo
2013-08-27 7:30 ` Michal Kazior
2013-08-28 4:02 ` Kalle Valo
2013-08-28 13:16 ` Michal Kazior
2013-08-26 20:20 ` [PATCH v2 0/4] ath10k: fixes Luis R. Rodriguez
2013-08-27 5:42 ` Michal Kazior
2013-08-27 7:59 ` Luis R. Rodriguez
2013-08-27 6:57 ` Kalle Valo
2013-08-27 8:01 ` Luis R. Rodriguez
2013-08-28 3:53 ` Kalle Valo [this message]
-- 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-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-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=87bo4ilbce.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.com \
--cc=rodrigue@qca.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).