archive mirror
 help / color / mirror / Atom feed
From: Paulo Alcantara <>
To: Moritz Duge <>,
	Thorsten Leemhuis <>
Cc: "" <>,
	Aurelien Aptel <>,
	Ronnie Sahlberg <>,
	Steve French <>,
	Linux Kernel Mailing List <>,
	"" <>
Subject: Re: Regression: CIFS umount fails since 14302ee33 with some servers (exit code 32)
Date: Wed, 04 May 2022 13:25:10 -0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Moritz Duge <> writes:

> I'm still waiting for a reply from Paul.

The bug is currently being handled at [1].  Enzo has also asked you to
send us network traces in [2] and you haven't sent any, yet.

I'm not "Paul", BTW.


  reply	other threads:[~2022-05-04 16:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 10:08 Regression: CIFS umount fails since 14302ee33 with some servers (exit code 32) Thorsten Leemhuis
2022-05-04 13:19 ` Thorsten Leemhuis
2022-05-04 16:12   ` Moritz Duge
2022-05-04 16:25     ` Paulo Alcantara [this message]
2022-05-04 16:43       ` Thorsten Leemhuis

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).