All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Cristian Marussi <cristian.marussi@arm.com>,
	arnd@kernel.org, lkp@intel.com
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	kbuild-all@lists.01.org, peter.hilber@opensynergy.com,
	igor.skalkin@opensynergy.com, linux-mm@kvack.org
Subject: Re: [PATCH] firmware: arm_scmi: Fix virtio transport Kconfig dependency
Date: Thu, 19 Aug 2021 06:39:33 +0100	[thread overview]
Message-ID: <162935143367.947810.560462950648362448.b4-ty@arm.com> (raw)
In-Reply-To: <20210816141609.41751-1-cristian.marussi@arm.com>

On Mon, 16 Aug 2021 15:16:09 +0100, Cristian Marussi wrote:
> ARM_SCMI_TRANSPORT_VIRTIO is a 'bool' Kconfig used to include support for
> the SCMI virtio transport inside the core SCMI stack; a bare transport
> dependency attached here to this option, though, cannot be properly
> propagated to the parent ARM_SCMI_PROTOCOL option and, as a result, it is
> currently possible to configure a Kernel where SCMI core is builtin
> and includes support for virtio while VirtIO core is =m.
> This allowed combination breaks linking:
> 
> [...]

Applied to sudeep.holla/linux (for-linux-next), thanks!

[1/1] firmware: arm_scmi: Fix virtio transport Kconfig dependency
      https://git.kernel.org/sudeep.holla/c/7b42623789
--
Regards,
Sudeep



WARNING: multiple messages have this Message-ID (diff)
From: Sudeep Holla <sudeep.holla@arm.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH] firmware: arm_scmi: Fix virtio transport Kconfig dependency
Date: Thu, 19 Aug 2021 06:39:33 +0100	[thread overview]
Message-ID: <162935143367.947810.560462950648362448.b4-ty@arm.com> (raw)
In-Reply-To: <20210816141609.41751-1-cristian.marussi@arm.com>

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

On Mon, 16 Aug 2021 15:16:09 +0100, Cristian Marussi wrote:
> ARM_SCMI_TRANSPORT_VIRTIO is a 'bool' Kconfig used to include support for
> the SCMI virtio transport inside the core SCMI stack; a bare transport
> dependency attached here to this option, though, cannot be properly
> propagated to the parent ARM_SCMI_PROTOCOL option and, as a result, it is
> currently possible to configure a Kernel where SCMI core is builtin
> and includes support for virtio while VirtIO core is =m.
> This allowed combination breaks linking:
> 
> [...]

Applied to sudeep.holla/linux (for-linux-next), thanks!

[1/1] firmware: arm_scmi: Fix virtio transport Kconfig dependency
      https://git.kernel.org/sudeep.holla/c/7b42623789
--
Regards,
Sudeep

  parent reply	other threads:[~2021-08-19  5:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-16 14:16 [PATCH] firmware: arm_scmi: Fix virtio transport Kconfig dependency Cristian Marussi
2021-08-16 14:16 ` Cristian Marussi
2021-08-16 14:30 ` Arnd Bergmann
2021-08-16 14:30   ` Arnd Bergmann
2021-08-16 14:47   ` Cristian Marussi
2021-08-16 14:47     ` Cristian Marussi
2021-08-16 15:29     ` Arnd Bergmann
2021-08-16 15:29       ` Arnd Bergmann
2021-08-19  5:39 ` Sudeep Holla [this message]
2021-08-19  5:39   ` 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=162935143367.947810.560462950648362448.b4-ty@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=arnd@kernel.org \
    --cc=cristian.marussi@arm.com \
    --cc=igor.skalkin@opensynergy.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=peter.hilber@opensynergy.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.