From: Paulo Alcantara <pc@manguebit.org>
To: Steve French <smfrench@gmail.com>
Cc: piastryyy@gmail.com, Xiaoli Feng <xifeng@redhat.com>,
Jay Shin <jaeshin@redhat.com>,
linux-cifs@vger.kernel.org
Subject: Re: [PATCH] cifscreds: fix parsing of commands and parameters
Date: Wed, 26 Nov 2025 13:02:05 -0300 [thread overview]
Message-ID: <615273d4ee88f4414d859e3e06d2afdd@manguebit.org> (raw)
In-Reply-To: <CAH2r5mutuLO4s6azh8g7D6Xs286mW_NyptEkF_6X3Uy4kY=FBw@mail.gmail.com>
Steve French <smfrench@gmail.com> writes:
> added to cifs-utils for-next
>
> Do you know if this is a regression of cifs-utils and if so what release/when?
It is regression introduced in cifs-utils-7.2.
next prev parent reply other threads:[~2025-11-26 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 19:55 [PATCH] cifscreds: fix parsing of commands and parameters Paulo Alcantara
2025-11-25 23:59 ` Steve French
2025-11-26 16:02 ` Paulo Alcantara [this message]
[not found] ` <CAKywueTatO7NNZ=020B27vFCLvA1yb0rsWGMgnB8PKV2-Pb=oQ@mail.gmail.com>
2025-12-01 17:35 ` Paulo Alcantara
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=615273d4ee88f4414d859e3e06d2afdd@manguebit.org \
--to=pc@manguebit.org \
--cc=jaeshin@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=piastryyy@gmail.com \
--cc=smfrench@gmail.com \
--cc=xifeng@redhat.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