From: apaul50 <apaul50@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Linux5.x series: Enable CONFIG_CIFS_SMB_DIRECT
Date: Thu, 30 Apr 2020 22:29:07 +0200 [thread overview]
Message-ID: <20200430202907.NXnNJk5Ja4gS2DZv-MtOKqEGYRfFtbJ2_wa9eEvYJEY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21374@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 707 bytes --]
New comment by apaul50 on void-packages repository
https://github.com/void-linux/void-packages/issues/21374#issuecomment-622092454
Comment:
@q66 After reading the description again, you may be right... I'm really confused. Since I recently switched on kernel 5.4.33, I'm not able to mount my office smb share (vers 2.0). If I boot on 4.19.114 I can mount it (provided I explicitly specify vers=2.0 option).
Watching the config file, I noticed CONFIG_CIFS_SMB311 wasn't present in 5.4 series, and maybe thought too fast it was replaced by CONFIG_CIFS_SMB_DIRECT... SMB311 seems to be merged in CONFIG_CIFS actually...
Guys, I'm really confused and ashamed... I've wasted your time... my apologies...
next prev parent reply other threads:[~2020-04-30 20:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 10:23 [ISSUE] Linux5.x series: CONFIG_CIFS_SMB_DIRECT apaul50
2020-04-29 8:17 ` Hoshpak
2020-04-29 13:27 ` apaul50
2020-04-30 9:31 ` Linux5.x series: Enable CONFIG_CIFS_SMB_DIRECT pullmoll
2020-04-30 11:10 ` pullmoll
2020-04-30 17:05 ` apaul50
2020-04-30 17:44 ` q66
2020-04-30 20:29 ` apaul50 [this message]
2020-04-30 20:58 ` q66
2020-04-30 22:08 ` apaul50
2020-05-05 21:22 ` apaul50
2021-08-31 18:09 ` ericonr
2021-08-31 18:09 ` [ISSUE] [CLOSED] " ericonr
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=20200430202907.NXnNJk5Ja4gS2DZv-MtOKqEGYRfFtbJ2_wa9eEvYJEY@z \
--to=apaul50@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).