From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: "Shajakhan, Mohammed Shafi (Mohammed Shafi)" <mohammed@qti.qualcomm.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
"mohammed@codeaurora.org" <mohammed@codeaurora.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] ath10k: remove duplicate and unused rx rate flags
Date: Thu, 2 Jun 2016 13:45:15 +0000 [thread overview]
Message-ID: <87a8j3zout.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1464852235-13110-1-git-send-email-mohammed@qca.qualcomm.com> (Mohammed Shafi Shajakhan's message of "Thu, 2 Jun 2016 12:53:54 +0530")
Mohammed Shafi Shajakhan <mohammed@qti.qualcomm.com> writes:
> From: Mohammed Shafi Shajakhan <mohammed@qti.qualcomm.com>
>
> All these flags are not used and their use is completely
> covered by 'ath10k_hw_rate_ofdm', 'ath10k_hw_rate_cck',
> and RX_PPDU_START_RATE_FLAG
>
> Signed-off-by: Mohammed Shafi Shajakhan <mohammed@qti.qualcomm.com>
> Patchwork-Id: 9129361
> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
I guess you took this patch from the pending branch? :) The Patchwork-Id
line is something which my script adds for patches in the pending
branch, and removes them before applying them to ath-next, but this line
should not be visible when submitting patches.
--
Kalle Valo
next prev parent reply other threads:[~2016-06-02 13:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 7:23 [PATCH v2 1/2] ath10k: remove duplicate and unused rx rate flags Mohammed Shafi Shajakhan
2016-06-02 7:23 ` [PATCH v2 2/2] ath10k: fix CCK h/w rates for QCA99X0 and newer chipsets Mohammed Shafi Shajakhan
2018-02-16 10:55 ` Sven Eckelmann
2016-06-02 13:45 ` Valo, Kalle [this message]
2016-06-02 14:22 ` [PATCH v2 1/2] ath10k: remove duplicate and unused rx rate flags Mohammed Shafi Shajakhan
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=87a8j3zout.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--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