All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cristian Marussi <cristian.marussi@arm.com>
To: Etienne Carriere <etienne.carriere@linaro.org>
Cc: "Ludvig Pärsson" <Ludvig.Parsson@axis.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"jens.wiklander@linaro.org" <jens.wiklander@linaro.org>,
	"sumit.garg@linaro.org" <sumit.garg@linaro.org>,
	"vincent.guittot@linaro.org" <vincent.guittot@linaro.org>,
	"sudeep.holla@arm.com" <sudeep.holla@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] firmware: arm_scmi: Resolve dependency with TEE subsystem
Date: Tue, 29 Nov 2022 17:30:50 +0000	[thread overview]
Message-ID: <Y4ZBypmGvVLrH5iT@e120937-lin> (raw)
In-Reply-To: <CAN5uoS8pFOLqZ3Jd7rHCisUcJvVkfWQqnOE=DUGyC3EURGLsFg@mail.gmail.com>

On Tue, Nov 29, 2022 at 03:57:50PM +0100, Etienne Carriere wrote:
> Hi Cristian, Ludvig,
> 

Hi Etienne,

> For info, I've tested your patches Cristian on my setup.
> they did the job for probing optee transport at module initcall level.
> 

Thanks for testing, I'll keep you in CC when posting the final series.
Cristian


WARNING: multiple messages have this Message-ID (diff)
From: Cristian Marussi <cristian.marussi@arm.com>
To: Etienne Carriere <etienne.carriere@linaro.org>
Cc: "Ludvig Pärsson" <Ludvig.Parsson@axis.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"jens.wiklander@linaro.org" <jens.wiklander@linaro.org>,
	"sumit.garg@linaro.org" <sumit.garg@linaro.org>,
	"vincent.guittot@linaro.org" <vincent.guittot@linaro.org>,
	"sudeep.holla@arm.com" <sudeep.holla@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] firmware: arm_scmi: Resolve dependency with TEE subsystem
Date: Tue, 29 Nov 2022 17:30:50 +0000	[thread overview]
Message-ID: <Y4ZBypmGvVLrH5iT@e120937-lin> (raw)
In-Reply-To: <CAN5uoS8pFOLqZ3Jd7rHCisUcJvVkfWQqnOE=DUGyC3EURGLsFg@mail.gmail.com>

On Tue, Nov 29, 2022 at 03:57:50PM +0100, Etienne Carriere wrote:
> Hi Cristian, Ludvig,
> 

Hi Etienne,

> For info, I've tested your patches Cristian on my setup.
> they did the job for probing optee transport at module initcall level.
> 

Thanks for testing, I'll keep you in CC when posting the final series.
Cristian


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-11-29 17:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  9:53 [PATCH] firmware: arm_scmi: Resolve dependency with TEE subsystem Sumit Garg
2022-11-11  9:53 ` Sumit Garg
2022-11-11 14:38 ` Sudeep Holla
2022-11-11 14:38   ` Sudeep Holla
2022-11-11 15:00   ` Ludvig Pärsson
2022-11-11 15:00     ` Ludvig Pärsson
2022-11-11 15:13     ` Sudeep Holla
2022-11-11 15:13       ` Sudeep Holla
2022-11-14  6:31   ` Sumit Garg
2022-11-14  6:31     ` Sumit Garg
2022-11-14 10:26     ` Sudeep Holla
2022-11-14 10:26       ` Sudeep Holla
2022-11-14 11:29       ` Etienne Carriere
2022-11-14 11:29         ` Etienne Carriere
2022-11-14 13:47         ` Ludvig Pärsson
2022-11-14 13:47           ` Ludvig Pärsson
2022-11-22 17:48           ` Cristian Marussi
2022-11-22 17:48             ` Cristian Marussi
2022-11-29 10:49             ` Ludvig Pärsson
2022-11-29 10:49               ` Ludvig Pärsson
2022-11-29 12:15               ` Cristian Marussi
2022-11-29 12:15                 ` Cristian Marussi
2022-11-29 14:57                 ` Etienne Carriere
2022-11-29 14:57                   ` Etienne Carriere
2022-11-29 17:30                   ` Cristian Marussi [this message]
2022-11-29 17:30                     ` Cristian Marussi
2022-11-17  9:41         ` Sumit Garg
2022-11-17  9:41           ` Sumit Garg
2022-11-17 11:19           ` Sudeep Holla
2022-11-17 11:19             ` Sudeep Holla

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=Y4ZBypmGvVLrH5iT@e120937-lin \
    --to=cristian.marussi@arm.com \
    --cc=Ludvig.Parsson@axis.com \
    --cc=etienne.carriere@linaro.org \
    --cc=jens.wiklander@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=sumit.garg@linaro.org \
    --cc=vincent.guittot@linaro.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.