From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable <stable@vger.kernel.org>,
Sasha Levin <alexander.levin@microsoft.com>
Subject: Re: Build problems in stable queue
Date: Fri, 4 May 2018 10:57:11 -0700 [thread overview]
Message-ID: <20180504175711.GA10296@roeck-us.net> (raw)
In-Reply-To: <20180504172608.GA4285@kroah.com>
On Fri, May 04, 2018 at 10:26:08AM -0700, Greg Kroah-Hartman wrote:
> On Fri, May 04, 2018 at 06:44:30AM -0700, Guenter Roeck wrote:
> > Couple of powerpc problems.
> >
> > 4.14, 4.16:
> >
> > drivers/net/ethernet/ibm/ibmvnic.c:1460:10: error: 'struct ibmvnic_tx_buff' has no member named 'num_entries'
> >
> > 3.18, 4.4:
> >
> > arch/powerpc/xmon/xmon.c:1180:7: error: 'xmon_on' undeclared
> >
> > Also, {i386,x86_64}:allnoconfig in 3.18:
> >
> > arch/x86/mm/pageattr.c:281:6: error: ‘kernel_set_to_readonly’ undeclared
> >
> > Most boot tests pass, except for a couple of powerpc tests where the image fails
> > to build.
>
> Ugh. I think I'm going to scrap all of these and let Sasha deal with
> the build/boot fallout before he resends them to me...
>
> I'll work on that over the next few days.
>
This scare has one advantage: I updated my merge script to let me merge random
branches (aka stable rc branches) into chromeos. Using this, I merged
v4.14.39-576-g237172570de5 and v4.4.131-268-g6d2832bac8de into the respective
ChromeOS branches. Currently testing...
Guenter
next prev parent reply other threads:[~2018-05-04 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 13:44 Build problems in stable queue Guenter Roeck
2018-05-04 17:26 ` Greg Kroah-Hartman
2018-05-04 17:57 ` Guenter Roeck [this message]
2018-05-04 20:41 ` Guenter Roeck
2018-05-04 22:11 ` Greg Kroah-Hartman
2018-05-04 22:47 ` Guenter Roeck
2018-05-05 2:27 ` Greg Kroah-Hartman
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=20180504175711.GA10296@roeck-us.net \
--to=linux@roeck-us.net \
--cc=alexander.levin@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.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