public inbox for linux-cifs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ralph Boehme <slow@samba.org>
To: Shyam Prasad N <nspmangalore@gmail.com>
Cc: linux-cifs@vger.kernel.org, smfrench@gmail.com, pc@manguebit.com,
	bharathsm@microsoft.com, dhowells@redhat.com,
	Shyam Prasad N <sprasad@microsoft.com>
Subject: Re: [PATCH] cifs: implementation id context as negotiate context
Date: Mon, 9 Mar 2026 18:35:48 +0100	[thread overview]
Message-ID: <031b8f1e-bd28-42e3-bcde-9bf73fe59b63@samba.org> (raw)
In-Reply-To: <CANT5p=p3V0Ap3EmZuh1ZYvg+-SgjyH-ZMmsakCdbzMMSL3KwJw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 516 bytes --]

Hi Shyam,

On 3/9/26 5:37 PM, Shyam Prasad N wrote:
> This can be useful for servers like Azure SMB servers, where it is not
> easy to explain client side behaviour without knowing what exact
> version of the code is running on the client.
so it is planned that MS is going to implement this in their servers?

I was kind of assuming this which made me wonder why is this made an 
community extension instead of a protocol feature will full MS backing 
including inclusion in MS-SMB2.

Thanks!
-slow


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2026-03-09 17:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04 12:27 [PATCH] cifs: implementation id context as negotiate context nspmangalore
2026-03-04 12:34 ` Shyam Prasad N
2026-03-06 22:45   ` Henrique Carvalho
2026-03-06 23:04     ` Steve French
2026-03-06 23:19       ` Paulo Alcantara
2026-03-06 23:23         ` Steve French
2026-03-09 16:34         ` Shyam Prasad N
2026-03-06 23:30       ` Henrique Carvalho
2026-03-09 16:19 ` Ralph Boehme
2026-03-09 16:37   ` Shyam Prasad N
2026-03-09 17:35     ` Ralph Boehme [this message]
2026-03-11 23:50       ` Shyam Prasad N
2026-03-09 17:59     ` Enzo Matsumiya
2026-03-11 23:52       ` Shyam Prasad N
2026-03-12  0:00         ` Steve French

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=031b8f1e-bd28-42e3-bcde-9bf73fe59b63@samba.org \
    --to=slow@samba.org \
    --cc=bharathsm@microsoft.com \
    --cc=dhowells@redhat.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=nspmangalore@gmail.com \
    --cc=pc@manguebit.com \
    --cc=smfrench@gmail.com \
    --cc=sprasad@microsoft.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