From: Sudeep Holla <sudeep.holla@arm.com>
To: Cristian Marussi <cristian.marussi@arm.com>
Cc: Adam Borowski <kilobyte@angband.pl>,
Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] firmware: arm_scmi: fix build failure if ARM_SCMI_PROTOCOL=y VIRTIO=m
Date: Mon, 13 Sep 2021 11:35:56 +0100 [thread overview]
Message-ID: <20210913103556.p2alen7xs3b6cjnp@bogus> (raw)
In-Reply-To: <20210913085501.GA22275@e120937-lin>
On Mon, Sep 13, 2021 at 09:55:01AM +0100, Cristian Marussi wrote:
> On Sun, Sep 12, 2021 at 11:27:25PM +0200, Adam Borowski wrote:
> > A "bool" for a subfeature doesn't force the dependency by itself.
> >
> > Signed-off-by: Adam Borowski <kilobyte@angband.pl>
> > ---
>
> Hi Adam,
>
> thanks for this fix, BUT it was already spotted by LKP
>
> https://lore.kernel.org/linux-mm/202108151230.lcHk2Pkk-lkp@intel.com/
>
> and a proposed fix is already queued on sudeep/for-next/scmi.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git/commit/?h=for-next/scmi&id=7b4262378924a9985bc4c35ea015bd48dfe57792
>
> I supposed it will picked up with the next 5.15 scmi fixes.
>
My bad, I must have replied as applied to that, on it now.
> Probably the original distribution list was a bit odd since I replied to
> the above original LKP mail recipients, apologies for this.
>
Could be for searching, but the tools grabbed the patch correctly without
any issues.
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-09-13 10:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-12 21:27 [PATCH] firmware: arm_scmi: fix build failure if ARM_SCMI_PROTOCOL=y VIRTIO=m Adam Borowski
2021-09-13 8:55 ` Cristian Marussi
2021-09-13 10:35 ` Sudeep Holla [this message]
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=20210913103556.p2alen7xs3b6cjnp@bogus \
--to=sudeep.holla@arm.com \
--cc=cristian.marussi@arm.com \
--cc=kilobyte@angband.pl \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox