From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Mohammed Shafi Shajakhan <mohammed@codeaurora.org>,
"Raja, Tamizh Chelvam" <c_traja@qti.qualcomm.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
"Shajakhan,
Mohammed Shafi (Mohammed Shafi)" <mohammed@qti.qualcomm.com>
Subject: Re: [PATCH 2/2] ath10k: Fix sending NULL/ Qos NULL data frames for QCA99X0 and later
Date: Thu, 30 Jun 2016 10:25:16 +0000 [thread overview]
Message-ID: <8760sr6kj8.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <576F2165.3010109@candelatech.com> (Ben Greear's message of "Sat, 25 Jun 2016 17:27:17 -0700")
Ben Greear <greearb@candelatech.com> writes:
> Is there a better way than posting to the ath10k mailing list? There are quite
> a few more of my patches that are stuck in pending or ignored state. If you
> could review some of them and add them to your testing trees then it might help
> them go upstream.
Yes, as you seem to test with your custom ath10k and custom firmware
review and testing feedback from others is more than welcome. That way I
can have more confidence that the patch really works with the mainline
version.
The problem with your patches is that you dump more responsibility on
me. I have no idea if they work with the mainline kernel, or if they
break something, so I need to personally test the patch and that takes
time. Basically I have a rule if that I need to use more than two
minutes on a patch it goes to the Deferred queue and I'll go through
that less often than the normal patch queue.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-06-30 10:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 16:40 [PATCH 1/2] ath10k: Replace warning with an error message if HTT op version is unset Mohammed Shafi Shajakhan
2016-06-23 16:40 ` [PATCH 2/2] ath10k: Fix sending NULL/ Qos NULL data frames for QCA99X0 and later Mohammed Shafi Shajakhan
2016-06-23 17:12 ` Ben Greear
2016-06-25 18:53 ` Mohammed Shafi Shajakhan
2016-06-26 0:27 ` Ben Greear
2016-06-30 10:25 ` Valo, Kalle [this message]
2016-07-05 15:21 ` Ben Greear
2016-07-08 11:00 ` Mohammed Shafi Shajakhan
2016-06-27 9:27 ` Michal Kazior
2016-06-27 14:36 ` Mohammed Shafi Shajakhan
2016-06-28 6:48 ` Michal Kazior
2016-06-29 9:47 ` Mohammed Shafi Shajakhan
[not found] ` <CAD2nsn3TOSaOCmm5YT6_D+aaoH9=pagQamDDz2VT+nKrFH0K8g@mail.gmail.com>
[not found] ` <900ae7541c5a4194a2f73479e1dd8bb2@aphydexm01b.ap.qualcomm.com>
2016-07-20 12:22 ` Michal Kazior
2016-07-20 16:27 ` Mohammed Shafi Shajakhan
2016-07-08 6:54 ` [1/2] ath10k: Replace warning with an error message if HTT op version is unset 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=8760sr6kj8.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=c_traja@qti.qualcomm.com \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mohammed@codeaurora.org \
--cc=mohammed@qti.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