From: Gao Xiang <gaoxiang25@huawei.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Greg KH <greg@kroah.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
Gao Xiang <hsiangkao@aol.com>, Chao Yu <yuchao0@huawei.com>
Subject: Re: linux-next: build warning after merge of the staging tree
Date: Mon, 26 Aug 2019 19:13:02 +0800 [thread overview]
Message-ID: <20190826111302.GA106991@architecture4> (raw)
In-Reply-To: <20190826095328.GA120601@architecture4>
On Mon, Aug 26, 2019 at 05:53:28PM +0800, Gao Xiang wrote:
[]
> The attempt above compiles successfully as well... And I have tried
> the following commands (Just in case...) and the result turns out
> without any difference...
>
> $ make ARCH=x86_64 allmodconfig
> $ make ARCH=x86_64 -j16
>
> and I'm so confused now... Hope to get your hints...
I think I got the warning now... Sorry, I thought it is a compile error.
I am looking into that, sorry about that...
Thanks,
Gao Xiang
>
> Thanks,
> Gao Xiang
>
> >
> > Out of curiosity, are there some merge conflicts raised? Or could you give
> > me some hints (code and .config) to reproduce that? since I don't find any
> > potential issue in include/trace/events/erofs.h and fs/erofs/*... I have no
> > idea what happened and how to do next... Thank you very much!
> >
> > Thanks,
> > Gao Xiang
> >
> > >
> > > Thanks,
> > > Gao Xiang
> > >
> > > > > >
> > > > > > Introduced by commit
> > > > > >
> > > > > > 47e4937a4a7c ("erofs: move erofs out of staging")
> > > > > >
> > > > > > (or, at least, exposed by it). It needs, at least, a "struct dentry;"
> > > > > > added to the file.
> > > > >
> > > > > Odd, why has this never been seen before when the same files were in
> > > > > drivers/staging/ and why 0-day isn't reporting this?
> > > >
> > > > I Think it is weird since it is never failed in staging and kbuild-all 0-day ci
> > > > (my tree and you tree)....
> > > >
> > > > >
> > > > > Gao, can you send me a patch for this?
> > > >
> > > > Got it, I will look into that...
> > > >
> > > > Thanks,
> > > > Gao Xiang
> > > >
> > > > >
> > > > > thanks,
> > > > >
> >
next prev parent reply other threads:[~2019-08-26 11:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 6:24 linux-next: build warning after merge of the staging tree Stephen Rothwell
2019-08-26 6:30 ` Greg KH
2019-08-26 8:38 ` Gao Xiang
2019-08-26 8:54 ` Gao Xiang
2019-08-26 9:43 ` Gao Xiang
2019-08-26 9:53 ` Gao Xiang
2019-08-26 11:13 ` Gao Xiang [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-09 7:16 Stephen Rothwell
2020-09-09 7:41 ` Greg KH
2019-12-13 1:10 Stephen Rothwell
2019-08-14 6:08 Stephen Rothwell
2019-08-14 7:42 ` Greg KH
2019-04-23 5:13 Stephen Rothwell
2018-11-08 2:33 Stephen Rothwell
2018-11-08 11:17 ` Greg KH
2018-09-03 2:06 Stephen Rothwell
2018-09-04 9:04 ` John Whitmore
2018-05-14 4:37 Stephen Rothwell
2018-01-16 2:45 Stephen Rothwell
2018-01-16 5:59 ` Greg KH
2018-01-16 10:47 ` Arnd Bergmann
2018-01-16 15:02 ` Greg KH
2017-01-20 4:36 Stephen Rothwell
2017-01-20 8:37 ` Greg KH
2017-01-20 9:18 ` Linus Walleij
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=20190826111302.GA106991@architecture4 \
--to=gaoxiang25@huawei.com \
--cc=greg@kroah.com \
--cc=hsiangkao@aol.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=yuchao0@huawei.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 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.