From: "Andrey Zhizhikin" <andrey.z@gmail.com>
To: Andrey Zhizhikin <andrey.z@gmail.com>
Cc: svdb <sam.van.den.berge@gmail.com>,
meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Update linux-fslc on hardknott branch
Date: Wed, 21 Jul 2021 13:27:37 +0200 [thread overview]
Message-ID: <CAHtQpK4pnm=LB3hgUHcPwWHCUg5RMXAMwx47y1nJKOYgOPvn6Q@mail.gmail.com> (raw)
In-Reply-To: <168FE8991221B0B8.11917@lists.yoctoproject.org>
Hello Sam,
On Thu, Jul 8, 2021 at 9:49 PM Andrey Zhizhikin via
lists.yoctoproject.org <andrey.z=gmail.com@lists.yoctoproject.org>
wrote:
>
> Hello Sam,
>
> On Thu, Jul 8, 2021 at 2:37 PM svdb <sam.van.den.berge@gmail.com> wrote:
> >
> > Hi,
> >
> > Currently on hardknott branch in meta-freescale, linux-fslc points to
> > version 5.10.32. However latest 5.10 version in linux-fslc repo is
> > 5.10.47. Would it be possible to update linux-fslc in meta-freescale on
> > hardknott branch?
>
> This is on my TODO list, see
> https://github.com/Freescale/meta-freescale/pull/814
>
> I'm pretty loaded now, but I'll see if I can bump up the version in
> recipes somewhen next week.
It took me quite a while, but I've submitted the PR against
[hardknott] to bump the kernel to the latest stable (both NXP and FSLC
ones).
See https://github.com/Freescale/meta-freescale/pull/831
>
> >
> > I don't mind creating some patches myself. I guess I'll need to
> > cherrypick the necessary commits from master then?
>
> Kernel tree already contains all stable updates, it is only about
> updating the kernel recipes in the layer.
>
> >
> > Kr,
> > Sam.
> >
> >
> >
> >
>
>
> --
> Regards,
> Andrey.
>
>
>
--
Regards,
Andrey.
prev parent reply other threads:[~2021-07-21 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 12:37 Update linux-fslc on hardknott branch svdb
2021-07-08 19:48 ` [meta-freescale] " Andrey Zhizhikin
[not found] ` <168FE8991221B0B8.11917@lists.yoctoproject.org>
2021-07-21 11:27 ` Andrey Zhizhikin [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='CAHtQpK4pnm=LB3hgUHcPwWHCUg5RMXAMwx47y1nJKOYgOPvn6Q@mail.gmail.com' \
--to=andrey.z@gmail.com \
--cc=meta-freescale@lists.yoctoproject.org \
--cc=sam.van.den.berge@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).