[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200809005036.GA100652@roeck-us.net>
Date: Sat, 8 Aug 2020 17:50:36 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Shuah Khan <skhan@...uxfoundation.org>,
Brendan Higgins <brendanhiggins@...gle.com>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Alan Maguire <alan.maguire@...cle.com>
Subject: Re: linux-next: build failure after merge of the thunderbolt tree
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
Powered by blists - more mailing lists