All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bajjuri, Praneeth" <praneeth@ti.com>
To: Denys Dmytriyenko <denis@denix.org>, Nishanth Menon <nm@ti.com>
Cc: meta-arago@arago-project.org
Subject: Re: [oe-layersetup][PATCH 0/2] arago-dunfell/dunfell-next: Move to
Date: Tue, 16 Mar 2021 14:13:09 -0500	[thread overview]
Message-ID: <a2a1382e-63fc-5d1b-d010-195b7a857679@ti.com> (raw)
In-Reply-To: <20210316184512.GJ18041@denix.org>



On 3/16/2021 1:45 PM, Denys Dmytriyenko wrote:
> On Tue, Mar 16, 2021 at 12:18:01PM -0500, Nishanth Menon wrote:
>> On 12:08-20210316, Nishanth Menon wrote:
>>
>> I have no idea what ate up my $subject -> I intended to add "Move to
>> dunfell/dunfell-tip from upstream.
>>
>>>
>>> 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.
>>
>> K, I might be missing the motivation here - the pinning may not be
>> required given that dunfell is always a rolling config.. and used only
>> in the cases of exceptions.. So, please ignore my comment.
> 
> Looks good to me.
> 
> Praneeth, I see you only merged one of two patches?

Yes , only pulled the dunfell-next config .. started the build job to 
check if builds are ok. Will pull the dunfell patch in couple of hrs.


> 


  reply	other threads:[~2021-03-16 19:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 17:08 [oe-layersetup][PATCH 0/2] arago-dunfell/dunfell-next: Move to Nishanth Menon
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 [this message]
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=a2a1382e-63fc-5d1b-d010-195b7a857679@ti.com \
    --to=praneeth@ti.com \
    --cc=denis@denix.org \
    --cc=meta-arago@arago-project.org \
    --cc=nm@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.