From: Al Viro <viro@zeniv.linux.org.uk>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: linux-next: build failures after merge of the vfs tree
Date: Tue, 16 Jun 2020 04:38:49 +0100 [thread overview]
Message-ID: <20200616033849.GL23230@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20200616010502.GA28834@gondor.apana.org.au>
On Tue, Jun 16, 2020 at 11:05:02AM +1000, Herbert Xu wrote:
> On Tue, Jun 16, 2020 at 10:34:40AM +1000, Stephen Rothwell wrote:
> > [Just adding Herbert to cc]
> >
> > On Tue, 16 Jun 2020 10:33:30 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > Hi all,
> > >
> > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig)
> > > failed like this:
>
> Thanks Stephen, here is an incremental patch to fix these up.
Folded and pushed
next prev parent reply other threads:[~2020-06-16 3:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 0:33 linux-next: build failures after merge of the vfs tree Stephen Rothwell
2020-06-16 0:34 ` Stephen Rothwell
2020-06-16 1:05 ` Herbert Xu
2020-06-16 3:38 ` Al Viro [this message]
2020-06-16 14:38 ` Herbert Xu
2020-06-16 15:14 ` Al Viro
2020-06-17 6:57 ` Stephen Rothwell
2020-06-17 7:03 ` Herbert Xu
2020-06-17 7:31 ` Stephen Rothwell
2020-06-17 7:38 ` Herbert Xu
2020-06-18 0:08 ` Stephen Rothwell
2020-06-30 1:58 ` Stephen Rothwell
2020-06-30 2:14 ` Herbert Xu
2020-06-30 13:36 ` Al Viro
2020-06-17 8:06 ` Stephen Rothwell
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=20200616033849.GL23230@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.