From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable <stable@vger.kernel.org>
Subject: Re: 4.14.y needs commit 71546d100422b
Date: Thu, 3 May 2018 08:28:37 -0700 [thread overview]
Message-ID: <20180503152837.GC23374@kroah.com> (raw)
In-Reply-To: <7716e533-4ef6-17ee-5a42-2be0381a44ad@roeck-us.net>
On Thu, May 03, 2018 at 06:36:35AM -0700, Guenter Roeck wrote:
> On 05/03/2018 04:53 AM, Greg Kroah-Hartman wrote:
> > On Wed, May 02, 2018 at 11:28:21PM -0700, Guenter Roeck wrote:
> > > Hi Greg,
> > >
> > > please pull commit 71546d100422b ("percpu: include linux/sched.h for cond_resched()")
> > > into v4.14.y to avoid build errors for microblaze and other architectures.
> >
> > Thanks, I'll do that, there's a bunch of build failures and warnings
> > right now to fix up. For most I'm just going to drop patches.
> >
> Sounds good. Note that 3.18.y needs the patch as well.
It does? Ok, I'll add it there.
> > > Also, with that many patches queued, can we possibly get more than the usual number
> > > of days for testing the next round of stable releases ?
> >
> > Oh yes, this is going to be a rough one :)
> >
> Yes, this one looks really bad. Not only build failures, but various architectures
> which do build fine don't even boot (including x86). You might want to have a look
> into my build system to get an idea, though I expect that 0day will keep you busy
> for a while. Let me know when you need specific feedback and/or help with specific
> problems.
Thanks, I think the new requirement for taking Sasha's patches is that
they at least pass 0-day first before sending them to me...
thanks,
greg k-h
next prev parent reply other threads:[~2018-05-03 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 6:28 4.14.y needs commit 71546d100422b Guenter Roeck
2018-05-03 11:53 ` Greg Kroah-Hartman
2018-05-03 13:36 ` Guenter Roeck
2018-05-03 15:28 ` Greg Kroah-Hartman [this message]
2018-05-03 15:29 ` Greg Kroah-Hartman
2018-05-03 15:57 ` Guenter Roeck
2018-05-03 16:11 ` 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=20180503152837.GC23374@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux@roeck-us.net \
--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 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.