From: Stephen Rothwell <sfr@rothwell.id.au>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Frank Rowand <frank.rowand@sony.com>,
Rob Herring <robh@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the overlayfs tree
Date: Wed, 31 Mar 2021 11:16:57 +1100 [thread overview]
Message-ID: <20210331111657.0babeb05@elm.ozlabs.ibm.com> (raw)
In-Reply-To: <CAJfpeguWeWp=648jtvaxNc+RFShTGDa=_gMDuq72qznt5LqQvw@mail.gmail.com>
Hi Miklos,
On Mon, 29 Mar 2021 11:28:10 +0200 Miklos Szeredi <miklos@szeredi.hu> wrote:
>
> On Mon, Mar 29, 2021 at 11:14 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Hi all,
> >
> > After merging the overlayfs tree, today's linux-next build (htmldocs)
>
> I think you mixed up drivers/of/overlay.c with fs/overlay/.
You are entirely correct and I have no idea how I managed that :-(
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2021-03-31 0:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 9:14 linux-next: build warning after merge of the overlayfs tree Stephen Rothwell
2021-03-29 9:28 ` Miklos Szeredi
2021-03-31 0:16 ` Stephen Rothwell [this message]
2021-04-21 6:26 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2021-07-20 6:38 Stephen Rothwell
2021-07-21 13:39 ` Miklos Szeredi
2017-11-08 22:33 Stephen Rothwell
2017-11-09 3:59 ` Chandan Rajendra
2017-05-17 0:19 Stephen Rothwell
2017-05-17 5:00 ` Amir Goldstein
2016-11-22 0:19 Stephen Rothwell
2016-11-22 8:41 ` Miklos Szeredi
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=20210331111657.0babeb05@elm.ozlabs.ibm.com \
--to=sfr@rothwell.id.au \
--cc=frank.rowand@sony.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=robh@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 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).