From: Kalle Valo <kvalo@codeaurora.org>
To: Chris Chiu <chiu@endlessos.org>
Cc: Pkshih <pkshih@realtek.com>, David Miller <davem@davemloft.net>,
kuba@kernel.org, linux-wireless <linux-wireless@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] rtlwifi: rtl8192se: remove duplicated legacy_httxpowerdiff
Date: Tue, 06 Oct 2020 09:02:37 +0300 [thread overview]
Message-ID: <87pn5vc2o2.fsf@codeaurora.org> (raw)
In-Reply-To: <CAB4CAwfaaozSbdiB05Mk-WgY1VQTyXtLNVjY+4vax09Qvr_asg@mail.gmail.com> (Chris Chiu's message of "Tue, 6 Oct 2020 12:02:12 +0800")
Chris Chiu <chiu@endlessos.org> writes:
> On Mon, Oct 5, 2020 at 11:01 PM Chris Chiu <chiu@endlessos.org> wrote:
>
> From: Chris Chiu <chiu@endlessos.org>
>
> The legacy_httxpowerdiff in rtl8192se is pretty much the same as
> the legacy_ht_txpowerdiff for other chips. Use the same name to
> keep the consistency.
>
> Signed-off-by: Chris Chiu <chiu@endlessos.org>
> ---
> drivers/net/wireless/realtek/rtlwifi/rtl8192se/hw.c | 2 +-
> drivers/net/wireless/realtek/rtlwifi/rtl8192se/rf.c | 2 +-
> drivers/net/wireless/realtek/rtlwifi/wifi.h | 1 -
> 3 files changed, 2 insertions(+), 3 deletions(-)
>
>
> Sorry. There's no patch series `PATCH 1/3` for this. I'll resubmit the
> patch.
Please don't send HTML mail, they will be dropped by mailing list and
patchwork.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2020-10-06 6:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 15:00 [PATCH 1/3] rtlwifi: rtl8192se: remove duplicated legacy_httxpowerdiff Chris Chiu
[not found] ` <CAB4CAwfaaozSbdiB05Mk-WgY1VQTyXtLNVjY+4vax09Qvr_asg@mail.gmail.com>
2020-10-06 6:02 ` Kalle Valo [this message]
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=87pn5vc2o2.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=chiu@endlessos.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pkshih@realtek.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 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.