On Mon, Nov 20, 2023 at 12:40:58PM -0500, Ihar Hrachyshka wrote:
> On Mon, Nov 20, 2023 at 11:22 AM Simon Horman wrote:
>
> > On Sat, Nov 18, 2023 at 01:07:02AM +, Ihar Hrachyshka wrote:
> > > In nonblocking mode, a POSIX socket may temporarily fail to connect(),
> > > which is indicated by r
On Mon, Nov 20, 2023 at 11:22 AM Simon Horman wrote:
> On Sat, Nov 18, 2023 at 01:07:02AM +, Ihar Hrachyshka wrote:
> > In nonblocking mode, a POSIX socket may temporarily fail to connect(),
> > which is indicated by returning EINPROGRESS. This patch will loop
> > waiting for connect() to suc
On Sat, Nov 18, 2023 at 01:07:02AM +, Ihar Hrachyshka wrote:
> In nonblocking mode, a POSIX socket may temporarily fail to connect(),
> which is indicated by returning EINPROGRESS. This patch will loop
> waiting for connect() to succeed, or until EINPROGRESS happens.
>
> An alternative - and p
Bleep bloop. Greetings Ihar Hrachyshka, I am a robot and I have tried out your
patch.
Thanks for your contribution.
I encountered some error that I wasn't expecting. See the details below.
checkpatch:
WARNING: The subject summary should end with a dot.
Subject: Loop to connect unix socket unt
In nonblocking mode, a POSIX socket may temporarily fail to connect(),
which is indicated by returning EINPROGRESS. This patch will loop
waiting for connect() to succeed, or until EINPROGRESS happens.
An alternative - and probably a better - path to deal with this error
would be to extend unix str
