From: Guenter Roeck <linux@roeck-us.net>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Shuah Khan <skhan@linuxfoundation.org>,
Brendan Higgins <brendanhiggins@google.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alan Maguire <alan.maguire@oracle.com>
Subject: Re: linux-next: build failure after merge of the thunderbolt tree
Date: Sat, 8 Aug 2020 17:50:36 -0700 [thread overview]
Message-ID: <20200809005036.GA100652@roeck-us.net> (raw)
In-Reply-To: <20200630113302.GN5180@lahna.fi.intel.com>
On Tue, Jun 30, 2020 at 02:33:02PM +0300, Mika Westerberg wrote:
> On Tue, Jun 30, 2020 at 04:03:46PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the thunderbolt tree, today's linux-next build (powerpc
> > allyesconfig) failed like this:
> >
> >
> > Caused by commit
> >
> > 54509f5005ca ("thunderbolt: Add KUnit tests for path walking")
> >
> > interacting with commit
> >
> > d4cdd146d0db ("kunit: generalize kunit_resource API beyond allocated resources")
> >
> > from the kunit-next tree.
>
> Thanks for reporting and fixing. The fix looks good to me.
Unfortunately, the fix didn't make it into mainline.
Building x86_64:allyesconfig ... failed
--------------
Error log:
drivers/thunderbolt/test.c: In function '__ida_init':
drivers/thunderbolt/test.c:20:5: error: 'struct kunit_resource' has no member named 'allocation'
20 | res->allocation = ida;
| ^~
drivers/thunderbolt/test.c: In function '__ida_destroy':
drivers/thunderbolt/test.c:26:23: error: 'struct kunit_resource' has no member named 'allocation'
26 | struct ida *ida = res->allocation;
| ^~
make[3]: *** [drivers/thunderbolt/test.o] Error 1
Guenter
next prev parent reply other threads:[~2020-08-09 0:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 6:03 linux-next: build failure after merge of the thunderbolt tree Stephen Rothwell
2020-06-30 9:27 ` Alan Maguire
2020-06-30 11:33 ` Mika Westerberg
2020-08-09 0:50 ` Guenter Roeck [this message]
2020-08-09 8:18 ` Stephen Rothwell
2020-08-09 18:04 ` Linus Torvalds
2020-08-09 23:10 ` Stephen Rothwell
2020-08-10 10:12 ` Mika Westerberg
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=20200809005036.GA100652@roeck-us.net \
--to=linux@roeck-us.net \
--cc=alan.maguire@oracle.com \
--cc=brendanhiggins@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=sfr@canb.auug.org.au \
--cc=skhan@linuxfoundation.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