public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Etienne Carriere <etienne.carriere@linaro.org>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>,
	 Sudeep Holla <sudeep.holla@arm.com>,
	kernel test robot <lkp@intel.com>
Subject: Re: [PATCH -next] firmware: arm_scmi: Fix the build when CONFIG_MAILBOX is not selected
Date: Thu, 3 Jun 2021 15:59:23 +0100	[thread overview]
Message-ID: <20210603145923.oxbis5ss3gjzha3t@bogus> (raw)
In-Reply-To: <CAN5uoS-N=EE21sd_gXh97xmyps_5Q=+YCz3TJqjUr=-qMjJpRw@mail.gmail.com>

On Thu, Jun 03, 2021 at 03:33:05PM +0200, Etienne Carriere wrote:
> On Thu, 3 Jun 2021 at 14:55, Cristian Marussi <cristian.marussi@arm.com> wrote:
> >
> > Reviewed-by: Cristian Marussi <cristian.marussi@arm.com>
> > Tested-by: Cristian Marussi <cristian.marussi@arm.com>
> 
> Likely related to "firmware: arm_scmi: fix deps arm-smccc-discovery
> deps in Kconfig"
> Thanks for the fix.
> 
> Reviewed-by: Etienne Carriere <etienne.carriere@linaro.org>

Thanks, indeed your patch triggered this but not it's fault though. That's
why though I initially thought of squashing this into your patch, decided
against it as this build fix must have been there once we abstracted
the mailbox transport. Hence I posted it as a separate patch.

-- 
Regards,
Sudeep

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

  reply	other threads:[~2021-06-03 15:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03  7:26 [PATCH -next] firmware: arm_scmi: Fix the build when CONFIG_MAILBOX is not selected Sudeep Holla
2021-06-03 12:55 ` Cristian Marussi
2021-06-03 13:33   ` Etienne Carriere
2021-06-03 14:59     ` Sudeep Holla [this message]
2021-06-04  8:55 ` 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=20210603145923.oxbis5ss3gjzha3t@bogus \
    --to=sudeep.holla@arm.com \
    --cc=cristian.marussi@arm.com \
    --cc=etienne.carriere@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lkp@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox