From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-cifs@vger.kernel.org" <linux-cifs@vger.kernel.org>,
linux-cifsd-devel@lists.sourceforge.net,
Hyunchul Lee <hyc.lee@gmail.com>,
Steve French <sfrench@samba.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Namjae Jeon <namjae.jeon@samsung.com>
Subject: Re: linux-next: Tree for Mar 18 (cifsd: Kconfig)
Date: Thu, 18 Mar 2021 11:57:36 -0700 [thread overview]
Message-ID: <3497bc60-51be-04ba-50c8-4bc258df7f31@infradead.org> (raw)
In-Reply-To: <20210318210844.5e9adf1e@canb.auug.org.au>
On 3/18/21 3:08 AM, Stephen Rothwell wrote:
> Hi all,
>
> News: there will be no linux-next release on Friday this week.
>
> Warning: Some of the branches in linux-next are still based on v5.12-rc1,
> so please be careful if you are trying to bisect a bug.
>
> News: if your -next included tree is based on Linus' tree tag
> v5.12-rc1{,-dontuse} (or somewhere between v5.11 and that tag), please
> consider rebasing it onto v5.12-rc2. Also, please check any branches
> merged into your branch.
>
> Changes since 20210317:
>
> The cifsd tree lost its build failure.
kconfig warning in cifsd:
WARNING: unmet direct dependencies detected for CRYPTO_ARC4
Depends on [n]: CRYPTO [=y] && CRYPTO_USER_API_ENABLE_OBSOLETE [=n]
Selected by [y]:
- SMB_SERVER [=y] && NETWORK_FILESYSTEMS [=y] && INET [=y]
Either
select CRYPTO_ARC4 if CRYPTO_USER_API_ENABLE_OBSOLETE
or add
select CRYPTO_USER_API
select CRYPTO_USER_API_ENABLE_OBSOLETE
The first choice is certainly more palatable if it is OK.
thanks.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
next prev parent reply other threads:[~2021-03-18 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 10:08 linux-next: Tree for Mar 18 Stephen Rothwell
2021-03-18 10:09 ` Stephen Rothwell
2021-03-18 18:57 ` Randy Dunlap [this message]
2021-03-19 1:00 ` linux-next: Tree for Mar 18 (cifsd: Kconfig) Namjae Jeon
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=3497bc60-51be-04ba-50c8-4bc258df7f31@infradead.org \
--to=rdunlap@infradead.org \
--cc=hyc.lee@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-cifsd-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=sfrench@samba.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
all inboxes | Powered by JetHome®