From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Stian Halseth <stian@itx.no>, axboe@kernel.dk
Cc: linux-block@vger.kernel.org, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org, andreas@gaisler.com,
davem@davemloft.net, regressions@lists.linux.dev
Subject: Re: [PATCH 0/2] sunvdc: fix silent data loss under LDC congestion
Date: Thu, 10 Sep 2026 09:14:25 +0200 [thread overview]
Message-ID: <774b2451be908e2cc07f0cc4d98e4178ab1a0d7b.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <20260901173947.3292110-1-stian@itx.no>
Hi Jens,
any chance you could take a look at this series?
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2026-09-10 7:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 10:02 [PATCH v2] Revert "sunvdc: Do not spin in an infinite loop when vio_ldc_send() returns EAGAIN" John Paul Adrian Glaubitz
2025-10-06 12:48 ` Jens Axboe
2025-10-06 13:00 ` John Paul Adrian Glaubitz
2025-10-06 13:03 ` John Paul Adrian Glaubitz
2025-10-06 13:19 ` Jens Axboe
2025-10-06 13:34 ` John Paul Adrian Glaubitz
2025-10-06 13:46 ` Jens Axboe
2025-10-06 13:56 ` John Paul Adrian Glaubitz
2025-10-06 14:03 ` Jens Axboe
2025-10-06 14:12 ` John Paul Adrian Glaubitz
2025-10-06 14:27 ` Jens Axboe
2025-10-06 14:48 ` John Paul Adrian Glaubitz
2025-10-06 14:52 ` Jens Axboe
2026-09-01 17:39 ` [PATCH 0/2] sunvdc: fix silent data loss under LDC congestion Stian Halseth
2026-09-01 17:39 ` [PATCH 1/2] sunvdc: unmap LDC cookies when the descriptor send fails Stian Halseth
2026-09-01 17:39 ` [PATCH 2/2] sunvdc: fix -EIO issue due to lack of retries Stian Halseth
2026-09-10 7:14 ` John Paul Adrian Glaubitz [this message]
2026-09-10 20:55 ` [PATCH 0/2] sunvdc: fix silent data loss under LDC congestion Jens Axboe
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=774b2451be908e2cc07f0cc4d98e4178ab1a0d7b.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=andreas@gaisler.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=sparclinux@vger.kernel.org \
--cc=stian@itx.no \
/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
all inboxes | Powered by JetHome®