All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: <praneeth@ti.com>, <denis@denix.org>
Cc: meta-arago@arago-project.org
Subject: [oe-layersetup][PATCH 0/2] arago-dunfell/dunfell-next: Move to
Date: Tue, 16 Mar 2021 12:08:55 -0500	[thread overview]
Message-ID: <20210316170857.9547-1-nm@ti.com> (raw)

Hi,

Series of patches to get ourselves synced with the latest
dunfell to pick up fixes from upstream - esp around thinprovisioning and
dropping our internal version of the fix for mariadb.

This brings arago-config and arago-next-config both in sync with latest
dunfell and dunfell-next tips appropriately.

This series obviously will need to be followed up at an appropriate time
with a stable commit sha patch to pin things up.

Nishanth Menon (2):
  Revert "arago-dunfell-next: Temporarily redirect meta-openembedded"
  Revert "arago-dunfell: Pin all layers to last known good build SHA"

 configs/arago-dunfell-config.txt      | 8 ++++----
 configs/arago-dunfell-next-config.txt | 3 +--
 2 files changed, 5 insertions(+), 6 deletions(-)

-- 
2.25.1.377.g2d2118b814c1



             reply	other threads:[~2021-03-16 17:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 17:08 Nishanth Menon [this message]
2021-03-16 17:08 ` [oe-layersetup][PATCH 1/2] Revert "arago-dunfell-next: Temporarily redirect meta-openembedded" Nishanth Menon
2021-03-16 17:08 ` [oe-layersetup][PATCH 2/2] Revert "arago-dunfell: Pin all layers to last known good build SHA" Nishanth Menon
2021-03-16 17:18 ` [oe-layersetup][PATCH 0/2] arago-dunfell/dunfell-next: Move to Nishanth Menon
2021-03-16 18:45   ` Denys Dmytriyenko
2021-03-16 19:13     ` Bajjuri, Praneeth
2021-03-16 19:15       ` Denys Dmytriyenko

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=20210316170857.9547-1-nm@ti.com \
    --to=nm@ti.com \
    --cc=denis@denix.org \
    --cc=meta-arago@arago-project.org \
    --cc=praneeth@ti.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.