From: Kalle Valo <kvalo@codeaurora.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Niklas Cassel <niklas.cassel@linaro.org>,
kbuild-all@01.org, "David S. Miller" <davem@davemloft.net>,
ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] ath10k: ath10k_snoc_get_ce_id_from_irq() can be static
Date: Wed, 13 Jun 2018 12:57:22 +0300 [thread overview]
Message-ID: <87d0wvau0t.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20180612145037.GA95182@lkp-ib03> (kbuild test robot's message of "Tue, 12 Jun 2018 22:50:37 +0800")
kbuild test robot <fengguang.wu@intel.com> writes:
> Fixes: aecf55e7df3a ("ath10k: allow ATH10K_SNOC with COMPILE_TEST")
> Signed-off-by: kbuild test robot <fengguang.wu@intel.com>
There's already an identical patch pending:
ath10k: make some functions static
https://patchwork.kernel.org/patch/10440159/
--
Kalle Valo
next prev parent reply other threads:[~2018-06-13 9:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 11:39 [PATCH 1/2] ath10k: do not mix spaces and tabs in Kconfig Niklas Cassel
2018-06-12 11:39 ` [PATCH 2/2] ath10k: allow ATH10K_SNOC with COMPILE_TEST Niklas Cassel
[not found] ` <7058492257914633b55fcd423e4c0b59@aphydexm01b.ap.qualcomm.com>
2018-06-12 12:32 ` FW: " Govind Singh
2018-06-12 12:44 ` Niklas Cassel
2018-06-13 8:47 ` Kalle Valo
2018-06-13 13:28 ` Niklas Cassel
2018-06-14 14:09 ` Kalle Valo
2018-06-14 18:42 ` Niklas Cassel
2018-06-12 14:50 ` [RFC PATCH] ath10k: ath10k_snoc_get_ce_id_from_irq() can be static kbuild test robot
2018-06-13 9:57 ` Kalle Valo [this message]
2018-06-12 14:50 ` [PATCH 2/2] ath10k: allow ATH10K_SNOC with COMPILE_TEST kbuild test robot
2018-06-13 9:56 ` Kalle Valo
2018-07-04 9:59 ` [2/2] " Kalle Valo
[not found] ` <20180704095913.772C9606AC@smtp.codeaurora.org>
2018-07-04 11:20 ` Niklas Cassel
2018-09-03 16:59 ` [PATCH 2/2] " Kalle Valo
2018-06-14 15:18 ` [1/2] ath10k: do not mix spaces and tabs in Kconfig 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=87d0wvau0t.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=niklas.cassel@linaro.org \
/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).