From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH v2 1/2] sae: check return on sae_send_commit()
Date: Thu, 5 Jun 2025 10:00:57 -0500 [thread overview]
Message-ID: <731bb193-8a15-42b3-b674-e83f9a00f35c@gmail.com> (raw)
In-Reply-To: <20250528192759.555623-1-prestwoj@gmail.com>
Hi James,
On 5/28/25 2:27 PM, James Prestwood wrote:
> If this fails, in some cases, -EAGAIN would be returned up to netdev
> which would then assume a retry would be done automatically. This
> would not in fact happen since it was an internal SAE failure which
> would result in the connect method return to never get sent.
>
> Now if sae_send_commit() fails, return -EPROTO which will cause
> netdev to fail the connection.
> ---
> src/sae.c | 14 ++++++++++----
> 1 file changed, 10 insertions(+), 4 deletions(-)
>
Applied, thanks.
Regards,
-Denis
prev parent reply other threads:[~2025-06-05 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 19:27 [PATCH v2 1/2] sae: check return on sae_send_commit() James Prestwood
2025-05-28 19:27 ` [PATCH v2 2/2] sae: prevent groups 21, 25, and 26 from being used James Prestwood
2025-06-05 15:00 ` Denis Kenzior [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=731bb193-8a15-42b3-b674-e83f9a00f35c@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=prestwoj@gmail.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