All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: Ashish <ashishm@mvista.com>
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization] Comment / Feedback to include RPI-4 patches on DUNFELL branch
Date: Thu, 23 Jul 2020 08:29:32 -0400	[thread overview]
Message-ID: <CADkTA4Mny9-1d8V5o4=85LVX5soNThjXZ7FxXdX4TDyROb91PQ@mail.gmail.com> (raw)
In-Reply-To: <QMcX.1595504908355333125.079B@lists.yoctoproject.org>

On Thu, Jul 23, 2020 at 7:48 AM Ashish <ashishm@mvista.com> wrote:
>
> Hi  Bruce / Christopher ,
>
> - Can you share comments / plan ahead of merging RPI-4 Xen patches on dunfell ?
>   Currently most of patches from Chris are being on master branch .
>    And since Dunfell is an LTS , are there any plan to have Xen on Raspberry Pi4 on Dunfell branch ?
>

Unfortunately no. These are functionality patches, so they aren't
appropriate to backport to dunfell. They are also not being tested
against equivalent dunfell branches from the other repos, so
backporting would be non-trivial.

> - Or we will be having these release patches from "Gatesgarth" release.
>   This can help us to understand in a better way.
>

Since they are in master now, they will be part of gatesgarth.

Bruce

>
>
>
>
>
> 



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

  reply	other threads:[~2020-07-23 12:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23 11:48 Comment / Feedback to include RPI-4 patches on DUNFELL branch Ashish
2020-07-23 12:29 ` Bruce Ashfield [this message]
2020-07-24  2:36   ` [meta-virtualization] " Christopher Clark
2020-07-24  4:37     ` Ashish
2020-07-26 20:17       ` [meta-virtualization] " Christopher Clark
2020-07-27  5:52         ` Ashish

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='CADkTA4Mny9-1d8V5o4=85LVX5soNThjXZ7FxXdX4TDyROb91PQ@mail.gmail.com' \
    --to=bruce.ashfield@gmail.com \
    --cc=ashishm@mvista.com \
    --cc=meta-virtualization@lists.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.