From: Florian Fainelli <f.fainelli@gmail.com>
To: Kalle Valo <kvalo@kernel.org>,
Vinayak Yadawad <vinayak.yadawad@broadcom.com>
Cc: johannes@sipsolutions.net, linux-wireless@vger.kernel.org,
Jithu Jance <jithu.jance@broadcom.com>
Subject: Re: [PATCH 1/1] cfg80211: Allow P2P client interface to indicate successful 4way handshake by port authorization
Date: Thu, 30 Jun 2022 11:19:51 -0700 [thread overview]
Message-ID: <b214600a-cf03-5677-2e87-4e5201488dcb@gmail.com> (raw)
In-Reply-To: <87v8sioe40.fsf@kernel.org>
On 6/29/22 23:32, Kalle Valo wrote:
> Vinayak Yadawad <vinayak.yadawad@broadcom.com> writes:
>
>>>> These kind of disclaimers do not belong to public lists.
>> This disclosure got added by mistake, I will resend the patch again if needed without the disclaimer footer.
>
> Also please don't top post or use HTML in emails, it's best to ditch
> Outlook when sending emails to upstream lists. More information in the
> wiki link below.
>
This submission ought to be more correct, even if it somehow ended up
with the same Message-Id:
https://lore.kernel.org/linux-wireless/ef25cb49fcb921df2e5d99e574f65e8a009cc52c.1655905440.git.vinayak.yadawad@broadcom.com/#r
--
Florian
prev parent reply other threads:[~2022-06-30 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 13:47 [PATCH 1/1] cfg80211: Allow P2P client interface to indicate successful 4way handshake by port authorization Vinayak Yadawad
2022-06-30 6:38 ` Vinayak Yadawad
2022-06-29 17:23 ` Kalle Valo
[not found] ` <CAMLe8U9R=TktuhY_baVyexKsvArw70wyT-k_=LLpkXASK0M9kw@mail.gmail.com>
2022-06-30 6:32 ` Kalle Valo
2022-06-30 18:19 ` Florian Fainelli [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=b214600a-cf03-5677-2e87-4e5201488dcb@gmail.com \
--to=f.fainelli@gmail.com \
--cc=jithu.jance@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=vinayak.yadawad@broadcom.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.