From: Andrei Gherzan <andrei@gherzan.ro>
To: Trevor Woerner <twoerner@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-raspberrypi][PATCH] linux-raspberrypi_4.4.bb: upgrade to 4.4.32
Date: Tue, 6 Dec 2016 15:43:34 +0000 [thread overview]
Message-ID: <20161206154334.GA1636@carbonA> (raw)
In-Reply-To: <20161129030324.GA2836@openSUSE-i7.site>
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
On Mon, Nov 28, 2016 at 10:03:24PM -0500, Trevor Woerner wrote:
> On Mon 2016-11-28 @ 05:52:38 PM, Khem Raj wrote:
> >
> > > On Nov 28, 2016, at 5:42 PM, Trevor Woerner <twoerner@gmail.com> wrote:
> > >
> > > On Mon 2016-11-28 @ 03:21:50 PM, Khem Raj wrote:
> > >> its at 4.4.35 now see
> > >> https://github.com/kraj/meta-raspberrypi/commits/kraj/master <https://github.com/kraj/meta-raspberrypi/commits/kraj/master>
> > >
> > > True. But there's no -rt patch for 4.4.35:
> > > https://www.kernel.org/pub/linux/kernel/projects/rt/4.4/
> > >
> > > The latest 4.4.y -rt patch is 4.4.32.
> > >
> > > Since I'm working on a separate recipe for 4.4.32-rt43 I guess I could just
> > > base it on 4.4.32 and let the non-rt-mainline advance to 4.4.35 :-)
> >
> > does it not apply cleanly on 4.4.35
>
> As luck would have it, it does!
> (minus one hunk from Makefile for something that had already been added)
>
> Tomorrow I'll do a boot test and submit the patch (unless the boot test fails,
> or someone else beats me to it)
It does apply on .35 too (with some very minor changes). So, I will
merge the other update patch. Thanks guys!
--
Andrei Gherzan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 817 bytes --]
prev parent reply other threads:[~2016-12-06 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 15:12 [meta-raspberrypi][PATCH] linux-raspberrypi_4.4.bb: upgrade to 4.4.32 Trevor Woerner
2016-11-28 23:21 ` Khem Raj
2016-11-29 1:42 ` Trevor Woerner
2016-11-29 1:52 ` Khem Raj
2016-11-29 3:03 ` Trevor Woerner
2016-12-06 15:43 ` Andrei Gherzan [this message]
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=20161206154334.GA1636@carbonA \
--to=andrei@gherzan.ro \
--cc=twoerner@gmail.com \
--cc=yocto@yoctoproject.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.