All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Jon Mason <jdmason@kudzu.us>
Cc: meta-arm@lists.yoctoproject.org
Subject: Re: [PATCH 1/4] optee-os: asm debug prefix fixes
Date: Wed, 31 Jul 2024 09:35:57 +0300	[thread overview]
Message-ID: <ZqnbTSo2JxV2m6wr@nuoska> (raw)
In-Reply-To: <ZqmrjL-EKud5PJSn@kudzu.us>

Hi,

On Tue, Jul 30, 2024 at 11:12:12PM -0400, Jon Mason wrote:
> On Tue, Jul 30, 2024 at 12:31:59PM +0300, Mikko Rapeli wrote:
> > Hi,
> > 
> > Is there something in these patches that is not ok for merging?
> 
> Sorry for the delay.
> 
> Something in CI was breaking and I was trying to isolate it to the
> individual patches, but the CI I'm running that is publicly available
> has been having issues (which I think are now resolved) and the
> internal one has been bogged down with a large number of reviews.
> 
> v2 that you just sent is now in master-next and hopefully will be
> happy when I get up tomorrow morning.

Ok then these optee changes are likely not causing issues, good to know.

I'll wait for the master branch update, can't see master-next changes.

Cheers,

-Mikko


  reply	other threads:[~2024-07-31  6:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-18 13:41 [PATCH 1/4] optee-os: asm debug prefix fixes Mikko Rapeli
2024-07-18 13:41 ` [PATCH 2/4] optee-os: remove absolute paths Mikko Rapeli
2024-07-18 13:41 ` [PATCH 3/4] optee-os-tadevkit: remove buildpaths INSANE_SKIP Mikko Rapeli
2024-07-18 13:41 ` [PATCH 4/4] optee-os: " Mikko Rapeli
2024-07-30  9:31 ` [PATCH 1/4] optee-os: asm debug prefix fixes Mikko Rapeli
2024-07-31  3:12   ` Jon Mason
2024-07-31  6:35     ` Mikko Rapeli [this message]
2024-07-31 12:57       ` Jon Mason
2024-08-01  5:43         ` Mikko Rapeli

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=ZqnbTSo2JxV2m6wr@nuoska \
    --to=mikko.rapeli@linaro.org \
    --cc=jdmason@kudzu.us \
    --cc=meta-arm@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.