From: Sudeep Holla <sudeep.holla@arm.com>
To: Rob Herring <robh@kernel.org>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
devicetree@vger.kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 6/8] dt-bindings: mailbox : arm, mhu: Fix arm, scpi example used here
Date: Mon, 31 May 2021 09:17:30 +0100 [thread overview]
Message-ID: <20210531081730.jckoxxntct3qmymq@bogus> (raw)
In-Reply-To: <CAL_JsqJw7VoJaGZp_u56k1B3+tbpOimnmhY-4mL7axPyXDTs2A@mail.gmail.com>
On Thu, May 27, 2021 at 03:07:39PM -0500, Rob Herring wrote:
> On Thu, May 27, 2021 at 11:25 AM Sudeep Holla <sudeep.holla@arm.com> wrote:
[...]
> > Just curious if this is built as past of the series as I am unable to hit
> > this issue. However I get this if I remove 5/8 which is adding the scpi
> > yaml schema. Am I missing something ?
>
> The automated check does try to apply series, but runs checks a patch
> at time and it resets the base if it gets an error on a patch. I think
> switching patch 5 and 6 order should fix things. Don't worry about
> that yet, I'll look at the rest of the series.
>
Ah OK, will re-order them. Thanks for the review.
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-05-31 8:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 18:27 [PATCH 0/8] dt-bindings: firmware: Convert SCPI and SCMI to json schema Sudeep Holla
2021-05-26 18:28 ` [PATCH 1/8] dt-bindings: firmware: arm, scpi: Move arm, scpi-shmem " Sudeep Holla
2021-05-27 20:25 ` Rob Herring
2021-05-31 8:15 ` Sudeep Holla
2021-05-31 8:20 ` Sudeep Holla
2021-06-01 13:37 ` Rob Herring
2021-06-01 13:53 ` Sudeep Holla
2021-05-26 18:28 ` [PATCH 2/8] dt-bindings: firmware: arm, scmi: Move arm, scmi-shmem " Sudeep Holla
2021-05-26 18:28 ` [PATCH 3/8] dt-bindings: firmware: juno, scpi: Move to sram.yaml " Sudeep Holla
2021-05-26 18:28 ` [PATCH 4/8] dt-bindings: firmware: amlogic, scpi: Move arm, scpi-shmem to " Sudeep Holla
2021-05-26 18:28 ` [PATCH 5/8] dt-bindings: firmware: arm,scpi: Convert " Sudeep Holla
2021-05-27 14:23 ` [PATCH 5/8] dt-bindings: firmware: arm, scpi: " Rob Herring
2021-05-27 16:17 ` [PATCH 5/8] dt-bindings: firmware: arm,scpi: " Sudeep Holla
2021-05-26 18:28 ` [PATCH 6/8] dt-bindings: mailbox : arm, mhu: Fix arm, scpi example used here Sudeep Holla
2021-05-27 14:23 ` Rob Herring
2021-05-27 16:25 ` Sudeep Holla
2021-05-27 20:07 ` Rob Herring
2021-05-31 8:17 ` Sudeep Holla [this message]
2021-05-26 18:28 ` [PATCH 7/8] dt-bindings: firmware: amlogic, scpi: Convert to json schema Sudeep Holla
2021-05-27 20:33 ` Rob Herring
2021-05-31 8:36 ` Sudeep Holla
2021-05-26 18:28 ` [PATCH 8/8] dt-bindings: firmware: arm,scmi: " Sudeep Holla
2021-05-26 18:35 ` Sudeep Holla
2021-05-27 20:15 ` [PATCH 8/8] dt-bindings: firmware: arm, scmi: " Rob Herring
2021-05-27 6:37 ` Etienne Carriere
2021-05-27 10:53 ` [PATCH 8/8] dt-bindings: firmware: arm,scmi: " Sudeep Holla
2021-05-27 10:33 ` Cristian Marussi
2021-05-27 10:49 ` 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=20210531081730.jckoxxntct3qmymq@bogus \
--to=sudeep.holla@arm.com \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).