From: "Valo, Kalle" <kvalo@qca.qualcomm.com> To: Marty Faltesek <mfaltesek@google.com> Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>, "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org> Subject: Re: [PATCH] ath10k: cache calibration data when the core is stopped. Date: Thu, 6 Oct 2016 07:40:48 +0000 [thread overview] Message-ID: <87r37ukjr5.fsf@kamboji.qca.qualcomm.com> (raw) In-Reply-To: <CAOiWkA_fuhzPeF7qPP0hLN3KTZUOi6_te5Zc3+vxKQ9GRj0VBw@mail.gmail.com> (Marty Faltesek's message of "Wed, 5 Oct 2016 12:39:48 -0400") Marty Faltesek <mfaltesek@google.com> writes: > On Mon, Oct 3, 2016 at 3:46 AM, Valo, Kalle <kvalo@qca.qualcomm.com> wrot= e: >> Marty Faltesek <mfaltesek@google.com> writes: >> >>> Caching calibration data allows it to be accessed when the >>> device is not active. >>> >>> Signed-off-by: Marty Faltesek <mfaltesek@google.com> >> >> No comma in the title, please. >> >> What tree did you use as the baseline? This doesn't seem to apply to >> ath.git: > > We use backports 20160122 which has not been updated since earlier this y= ear. > I can forward port it to your tree, and make sure > it builds but won't be able to test it. Will that be OK? Sure, I can test it. >> Also please note that this patch (which I'm queuing to 4.9) touches the >> same area: >> >> ath10k: fix debug cal data file >> >> https://patchwork.kernel.org/patch/9340953/ > > I've modified this too, and this won't be necessary, so can you drop > it? If not, let me know and I'll pull it in and make sure I'm based > off it too. Actually I was first planning to push 9340953 to 4.9 and take your patch to 4.10. But your patch is a cleaner approach to this and maybe I should push that to 4.9 instead? Need to think a bit more. --=20 Kalle Valo=
WARNING: multiple messages have this Message-ID (diff)
From: "Valo, Kalle" <kvalo@qca.qualcomm.com> To: Marty Faltesek <mfaltesek@google.com> Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>, "ath10k@lists.infradead.org" <ath10k@lists.infradead.org> Subject: Re: [PATCH] ath10k: cache calibration data when the core is stopped. Date: Thu, 6 Oct 2016 07:40:48 +0000 [thread overview] Message-ID: <87r37ukjr5.fsf@kamboji.qca.qualcomm.com> (raw) In-Reply-To: <CAOiWkA_fuhzPeF7qPP0hLN3KTZUOi6_te5Zc3+vxKQ9GRj0VBw@mail.gmail.com> (Marty Faltesek's message of "Wed, 5 Oct 2016 12:39:48 -0400") Marty Faltesek <mfaltesek@google.com> writes: > On Mon, Oct 3, 2016 at 3:46 AM, Valo, Kalle <kvalo@qca.qualcomm.com> wrote: >> Marty Faltesek <mfaltesek@google.com> writes: >> >>> Caching calibration data allows it to be accessed when the >>> device is not active. >>> >>> Signed-off-by: Marty Faltesek <mfaltesek@google.com> >> >> No comma in the title, please. >> >> What tree did you use as the baseline? This doesn't seem to apply to >> ath.git: > > We use backports 20160122 which has not been updated since earlier this year. > I can forward port it to your tree, and make sure > it builds but won't be able to test it. Will that be OK? Sure, I can test it. >> Also please note that this patch (which I'm queuing to 4.9) touches the >> same area: >> >> ath10k: fix debug cal data file >> >> https://patchwork.kernel.org/patch/9340953/ > > I've modified this too, and this won't be necessary, so can you drop > it? If not, let me know and I'll pull it in and make sure I'm based > off it too. Actually I was first planning to push 9340953 to 4.9 and take your patch to 4.10. But your patch is a cleaner approach to this and maybe I should push that to 4.9 instead? Need to think a bit more. -- Kalle Valo _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-10-06 7:43 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-09-13 21:11 [PATCH] ath10k: cache calibration data when the core is stopped Marty Faltesek 2016-09-13 21:11 ` Marty Faltesek 2016-10-03 7:46 ` Valo, Kalle 2016-10-03 7:46 ` Valo, Kalle 2016-10-05 16:39 ` Marty Faltesek 2016-10-05 16:39 ` Marty Faltesek 2016-10-06 7:40 ` Valo, Kalle [this message] 2016-10-06 7:40 ` Valo, Kalle 2016-10-06 20:29 ` Marty Faltesek 2016-10-06 20:29 ` Marty Faltesek 2016-10-03 7:51 ` Valo, Kalle 2016-10-03 7:51 ` Valo, Kalle 2016-10-03 8:02 ` Michal Kazior 2016-10-03 8:02 ` Michal Kazior 2016-10-05 16:40 ` Marty Faltesek 2016-10-05 16:40 ` Marty Faltesek
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=87r37ukjr5.fsf@kamboji.qca.qualcomm.com \ --to=kvalo@qca.qualcomm.com \ --cc=ath10k@lists.infradead.org \ --cc=linux-wireless@vger.kernel.org \ --cc=mfaltesek@google.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: linkBe 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.