From: Mohsin Bashir <mohsin.bashr@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>, netdev@vger.kernel.org
Cc: alexanderduyck@fb.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, horms@kernel.org,
jacob.e.keller@intel.com, kernel-team@meta.com, kuba@kernel.org,
lee@trager.us, sanman.p211993@gmail.com, mohsin.bashr@gmail.com
Subject: Re: [PATCH net-next V2 5/5] eth: fbnic: Update RX mbox timeout value
Date: Tue, 20 Jan 2026 13:43:31 -0800 [thread overview]
Message-ID: <de37782d-a969-4f02-b7fe-355bdbe63d6f@gmail.com> (raw)
In-Reply-To: <d9096361-8f51-4865-af59-531649a5f42e@redhat.com>
> Timeout for all events is now 10 seconds. Is that intentional? Could
> that cause unexpected timeout on flash update?
>
Hi Paolo,
Yes, we intentionally set it to 10 sec.
> /P
>
next prev parent reply other threads:[~2026-01-20 21:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 0:33 [PATCH net-next V2 0/5] eth: fbnic: Update IPC mailbox support Mohsin Bashir
2026-01-15 0:33 ` [PATCH net-next V2 1/5] eth: fbnic: Use GFP_KERNEL to allocting mbx pages Mohsin Bashir
2026-01-15 0:33 ` [PATCH net-next V2 2/5] eth: fbnic: Allocate all pages for RX mailbox Mohsin Bashir
2026-01-15 0:33 ` [PATCH net-next V2 3/5] eth: fbnic: Reuse RX mailbox pages Mohsin Bashir
2026-01-15 0:33 ` [PATCH net-next V2 4/5] eth: fbnic: Remove retry support Mohsin Bashir
2026-01-15 0:33 ` [PATCH net-next V2 5/5] eth: fbnic: Update RX mbox timeout value Mohsin Bashir
2026-01-20 10:04 ` Paolo Abeni
2026-01-20 21:43 ` Mohsin Bashir [this message]
2026-01-21 2:30 ` [PATCH net-next V2 0/5] eth: fbnic: Update IPC mailbox support patchwork-bot+netdevbpf
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=de37782d-a969-4f02-b7fe-355bdbe63d6f@gmail.com \
--to=mohsin.bashr@gmail.com \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=lee@trager.us \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sanman.p211993@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 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.