From: YueHaibing <yuehaibing@huawei.com>
To: Brian Norris <briannorris@chromium.org>
Cc: Kalle Valo <kvalo@codeaurora.org>, <ath10k@lists.infradead.org>,
<netdev@vger.kernel.org>, <linux-wireless@vger.kernel.org>,
<kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH] ath10k: snoc: remove set but not used variable 'ar_snoc'
Date: Wed, 30 Jan 2019 09:31:51 +0800 [thread overview]
Message-ID: <a2b059fe-e527-0cff-2114-26f5bdaf7443@huawei.com> (raw)
In-Reply-To: <CA+ASDXMQto_dqPOuUEX9vqqbWmor8qvpwxBVTg6tSnHkfsCzpw@mail.gmail.com>
On 2019/1/30 2:12, Brian Norris wrote:
> On Mon, Jan 28, 2019 at 9:53 PM YueHaibing <yuehaibing@huawei.com> wrote:
>>
>> ping...
>
> For some reason, your patch shows up as Deferred in patchwork:
>
> https://patchwork.kernel.org/patch/10589789/
>
> So the maintainers have accidentally (?) ignored it. I'm not what the
> official suggestion is for that, but you might just resend.
Thank you for your review, I'll resend it.
>
> In any case...
>
>> On 2018/9/6 10:29, YueHaibing wrote:
>>> From: Yue Haibing <yuehaibing@huawei.com>
>>>
>>> Fixes gcc '-Wunused-but-set-variable' warning:
>>>
>>> drivers/net/wireless/ath/ath10k/snoc.c: In function 'ath10k_snoc_tx_pipe_cleanup':
>>> drivers/net/wireless/ath/ath10k/snoc.c:681:22: warning:
>>> variable 'ar_snoc' set but not used [-Wunused-but-set-variable]
>>>
>>> Signed-off-by: Yue Haibing <yuehaibing@huawei.com>
>
> ...patch looks fine to me:
>
> Reviewed-by: Brian Norris <briannorris@chromium.org>
>
>
next prev parent reply other threads:[~2019-01-30 1:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 2:29 [PATCH] ath10k: snoc: remove set but not used variable 'ar_snoc' YueHaibing
2019-01-29 5:53 ` YueHaibing
2019-01-29 18:12 ` Brian Norris
2019-01-30 1:31 ` YueHaibing [this message]
2019-01-30 10:32 ` 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=a2b059fe-e527-0cff-2114-26f5bdaf7443@huawei.com \
--to=yuehaibing@huawei.com \
--cc=ath10k@lists.infradead.org \
--cc=briannorris@chromium.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.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).