linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org, Ping-Ke Shih <pkshih@realtek.com>,
	Yan-Hsuan Chuang <yhchuang@realtek.com>,
	Birming Chiu <birming@realtek.com>, Shaofu <shaofu@realtek.com>,
	Steven Ting <steventing@realtek.com>
Subject: Re: [PATCH v4 01/10] rtlwifi: Fill in_4way field by driver
Date: Tue, 25 Jul 2017 15:20:39 +0300	[thread overview]
Message-ID: <87bmo8k8rs.fsf@codeaurora.org> (raw)
In-Reply-To: <20170702181239.17911-2-Larry.Finger@lwfinger.net> (Larry Finger's message of "Sun, 2 Jul 2017 13:12:30 -0500")

Larry Finger <Larry.Finger@lwfinger.net> writes:

> From: Ping-Ke Shih <pkshih@realtek.com>
>
> Because it isn't always correct to use EAPOL to check 4-way,
> we add a timer to handle exception.
>
> Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> Cc: Yan-Hsuan Chuang <yhchuang@realtek.com>
> Cc: Birming Chiu <birming@realtek.com>
> Cc: Shaofu <shaofu@realtek.com>
> Cc: Steven Ting <steventing@realtek.com>
> ---
> v2 - no changes
> v3 - no changes
> v4 - no changes

BTW, for my sake you don't need to have changelogs for every patch. For
me it's enough (and what I also prefer) that the cover letter contains
the changelog.

-- 
Kalle Valo

  reply	other threads:[~2017-07-25 12:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-02 18:12 [PATCH v3 00/10] Set 3 of changes related to updates of btcoexist Larry Finger
2017-07-02 18:12 ` [PATCH v4 01/10] rtlwifi: Fill in_4way field by driver Larry Finger
2017-07-25 12:20   ` Kalle Valo [this message]
2017-07-27  9:54   ` Kalle Valo
2017-07-27  9:56     ` Arend van Spriel
2017-07-27 10:08       ` Kalle Valo
2017-07-28 15:17   ` [v4,01/10] " Kalle Valo
2017-07-28 15:20     ` Kalle Valo
2017-07-02 18:12 ` [PATCH v4 02/10] rtlwifi: Add BT_MP_INFO to c2h handler Larry Finger
2017-07-03 21:08   ` Arend Van Spriel
2017-07-25 12:18     ` Kalle Valo
2017-07-27  9:59   ` Kalle Valo
2017-07-02 18:12 ` [PATCH v4 03/10] rtlwifi: Add board type for 8723be and 8192ee Larry Finger
2017-07-02 18:12 ` [PATCH v4 04/10] rtlwifi: add amplifier type for 8812ae Larry Finger
2017-07-02 18:12 ` [PATCH v4 05/10] rtlwifi: Update 8723be new phy parameters and its parser Larry Finger
2017-07-02 18:12 ` [PATCH v4 06/10] rtlwifi: Rename rtl_desc92_rate to rtl_desc_rate Larry Finger
2017-07-02 18:12 ` [PATCH v4 07/10] rtlwifi: Uses addr1 instead DA to determine broadcast and multicast addr Larry Finger
2017-07-02 18:12 ` [PATCH v4 08/10] rtlwifi: move IS_HARDWARE_TYPE_xxx checker to wifi.h Larry Finger
2017-07-02 18:12 ` [PATCH v4 09/10] rtlwifi: use debugfs to debug Larry Finger
2017-07-27 10:17   ` Kalle Valo
2017-07-27 10:39     ` Arend van Spriel
2017-07-27 10:56       ` Kalle Valo
2017-07-27 10:24   ` Kalle Valo
2017-07-28 15:22   ` [v4,09/10] " Kalle Valo
2017-07-02 18:12 ` [PATCH v4 10/10] rtlwifi: btcoex: Use seq_file to dump btcoex status Larry Finger

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=87bmo8k8rs.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=birming@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=shaofu@realtek.com \
    --cc=steventing@realtek.com \
    --cc=yhchuang@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 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).