From: Christoph Hellwig <hch@infradead.org>
To: Tom Talpey <tom@talpey.com>
Cc: Namjae Jeon <linkinjeon@kernel.org>,
Christoph Hellwig <hch@lst.de>,
Christoph Hellwig <hch@infradead.org>,
Steve French <smfrench@gmail.com>,
CIFS <linux-cifs@vger.kernel.org>,
Hyeoncheol Lee <hyc.lee@gmail.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: Regarding to how ksmbd handles sector size request from windows cllient
Date: Wed, 30 Mar 2022 21:06:57 -0700 [thread overview]
Message-ID: <YkUo4eLuQ8d4k2cF@infradead.org> (raw)
In-Reply-To: <84c7d6a4-f3e8-420e-828c-5852e21f1b08@talpey.com>
Leave is as-is. 128kb is not a valid sector size in Linux to start
with. That is what people get for using weird out of tree crap.
prev parent reply other threads:[~2022-03-31 4:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 7:53 Regarding to how ksmbd handles sector size request from windows cllient Namjae Jeon
2022-03-30 9:05 ` Christoph Hellwig
2022-03-30 13:46 ` Namjae Jeon
2022-03-30 12:09 ` Tom Talpey
2022-03-30 23:32 ` Namjae Jeon
2022-03-30 23:44 ` Tom Talpey
2022-03-31 4:06 ` Christoph Hellwig [this message]
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=YkUo4eLuQ8d4k2cF@infradead.org \
--to=hch@infradead.org \
--cc=hch@lst.de \
--cc=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=senozhatsky@chromium.org \
--cc=smfrench@gmail.com \
--cc=tom@talpey.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