All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fabio Estevam" <festevam@gmail.com>
To: Val Kondratenko <valeriy.kondratenko@jci.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>,
	 "meta-freescale@lists.yoctoproject.org"
	<meta-freescale@lists.yoctoproject.org>
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?
Date: Wed, 23 Jun 2021 17:05:56 -0300	[thread overview]
Message-ID: <CAOMZO5CU36pPQCjtakmmKcbHd41exnTSv4dje=BV-h4rbQcJ2A@mail.gmail.com> (raw)
In-Reply-To: <BN6P132MB00681AFE3BEB56EDCCBBC0B3E1089@BN6P132MB0068.NAMP132.PROD.OUTLOOK.COM>

On Wed, Jun 23, 2021 at 2:48 PM Val Kondratenko
<valeriy.kondratenko@jci.com> wrote:
>
> .. will probably be going to mainline uboot as well.
>
> Are there any similar things (like cpuidle moving from kernel to uboot), that I would have to worry about?

No, you should be good with tha mainline U-Boot and kernel combination.

  reply	other threads:[~2021-06-23 20:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 12:34 Safe to upgrade to a Community BSP? Val Kondratenko
2021-06-10 19:43 ` [meta-freescale] " Otavio Salvador
2021-06-10 20:18   ` Val Kondratenko
2021-06-10 21:11     ` Fabio Estevam
2021-06-11 15:12       ` Val Kondratenko
2021-06-11 16:19         ` Fabio Estevam
2021-06-11 16:42           ` Val Kondratenko
2021-07-09 19:22           ` Val Kondratenko
2021-06-23 17:48       ` Val Kondratenko
2021-06-23 20:05         ` Fabio Estevam [this message]
     [not found]       ` <16878FD7EE6FE05F.27948@lists.yoctoproject.org>
2021-06-25 17:53         ` Val Kondratenko
2021-06-25 18:11           ` Fabio Estevam
2021-06-29 20:03             ` Val Kondratenko
2021-07-06 14:29               ` Val Kondratenko
     [not found]         ` <168BE6901ABD95ED.20408@lists.yoctoproject.org>
2021-06-25 18:28           ` Val Kondratenko
2021-07-09 19:08   ` Val Kondratenko
2021-06-10 20:14 ` Fabio Estevam
2021-06-10 20:21   ` Val Kondratenko
2021-07-07 11:48 ` Val Kondratenko

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='CAOMZO5CU36pPQCjtakmmKcbHd41exnTSv4dje=BV-h4rbQcJ2A@mail.gmail.com' \
    --to=festevam@gmail.com \
    --cc=meta-freescale@lists.yoctoproject.org \
    --cc=otavio.salvador@ossystems.com.br \
    --cc=valeriy.kondratenko@jci.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 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.