From: Alakesh Haloi <alakeshh@amazon.com>
To: <gregkh@linuxfoundation.org>
Cc: <stable@vger.kernel.org>, Steve French <stfrench@microsoft.com>
Subject: Request for inclusion into linux-4.14.y
Date: Mon, 21 Jan 2019 19:35:43 +0000 [thread overview]
Message-ID: <20190121193530.GA72263@dev-dsk-alakeshh-2c-f8a3e6e0.us-west-2.amazon.com> (raw)
Hello Greg,
Can you please consider including the following patch in the stable
linux-4.14.y branch? This is to fix a broken dependency for config option
CONFIG_CIFS_POSIX
04f67ed3d83a ("cifs: allow disabling insecure dialects in the config")
Following commit introduced a dependency for CONFIG_CIFS_POSIX on the config
CONFIG_CIFS_ALLOW_INSECURE_LEGACY, but the above mentioned commit that had
enable CONFIG_CIFS_POSIX in 4.14.94.
ab9697222a1d ("cifs: In Kconfig CONFIG_CIFS_POSIX needs depends on legacy
(insecure cifs)")
Regards
-Alakesh Haloi
next reply other threads:[~2019-01-21 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 19:35 Alakesh Haloi [this message]
2019-01-21 19:44 ` Request for inclusion into linux-4.14.y Greg KH
2019-01-21 21:05 ` Alakesh Haloi
2019-01-24 18:02 ` Greg KH
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=20190121193530.GA72263@dev-dsk-alakeshh-2c-f8a3e6e0.us-west-2.amazon.com \
--to=alakeshh@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=stfrench@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;
as well as URLs for NNTP newsgroup(s).