LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: broonie@kernel.org, Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	akpm@linux-foundation.org,
	Linux FS-devel Mailing List <linux-fsdevel@vger.kernel.org>,
	Chuck Lever <chuck.lever@oracle.com>,
	linux-nfs@vger.kernel.org
Subject: Re: linux-next: Tree for Feb 22 (NFSD_V2_ACL)
Date: Tue, 22 Feb 2022 22:08:57 -0800	[thread overview]
Message-ID: <5ef34a6f-c8ed-bb32-db24-050398c897a0@infradead.org> (raw)
In-Reply-To: <20220223014135.2764641-1-broonie@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 554 bytes --]



On 2/22/22 17:41, broonie@kernel.org wrote:
> Hi all,
> 
> Note that today's -next does not include the akpm tree since it's been a
> long day and the conflicts seemed more than it was wise for me to
> attempt at this point.  I'll have another go tomorrow but no guarantees.
> 
> Changes since 20220217:
> 


on x86_64:

WARNING: unmet direct dependencies detected for NFSD_V2_ACL
  Depends on [n]: NETWORK_FILESYSTEMS [=y] && NFSD [=n]
  Selected by [y]:
  - NFSD_V3_ACL [=y] && NETWORK_FILESYSTEMS [=y]


Full randconfig file is attached.

-- 
~Randy

[-- Attachment #2: config-r2276.gz --]
[-- Type: application/gzip, Size: 31481 bytes --]

  parent reply	other threads:[~2022-02-23  6:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23  1:41 linux-next: Tree for Feb 22 broonie
2022-02-23  6:05 ` linux-next: Tree for Feb 22 (NET_DSA_SMSC_LAN9303) Randy Dunlap
2022-02-23  6:08 ` Randy Dunlap [this message]
2022-02-23 15:58   ` linux-next: Tree for Feb 22 (NFSD_V2_ACL) Chuck Lever III
2022-02-24  6:45     ` Randy Dunlap
2022-02-24 15:08       ` Chuck Lever III
2022-02-24 16:37         ` Randy Dunlap
2022-02-24 16:45           ` Chuck Lever III

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=5ef34a6f-c8ed-bb32-db24-050398c897a0@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --subject='Re: linux-next: Tree for Feb 22 (NFSD_V2_ACL)' \
    /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

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).