[PATCH v2 2/7] dt-bindings: hypervisor: Add MediaTek GenieZone hypervisor

Yi-De Wu (吳一德) Yi-De.Wu at mediatek.com
Sun May 21 20:45:23 PDT 2023


On Fri, 2023-05-12 at 09:34 -0700, Trilok Soni wrote:
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> 
> 
> On 5/11/2023 11:42 PM, Yi-De Wu (吳一德) wrote:
> > On Fri, 2023-04-28 at 09:52 -0500, Rob Herring wrote:
> > > External email : Please do not click links or open attachments
> > > until
> > > you have verified the sender or the content.
> > > 
> > > 
> > > On Fri, 28 Apr 2023 18:36:17 +0800, Yi-De Wu wrote:
> > > > From: "Yingshiuan Pan" <yingshiuan.pan at mediatek.com>
> > > > 
> > > > Add documentation for GenieZone(gzvm) node. This node informs
> > > > gzvm
> > > > driver to start probing if geniezone hypervisor is available
> > > > and
> > > > able to do virtual machine operations.
> > > > 
> > > > Signed-off-by: Yingshiuan Pan <yingshiuan.pan at mediatek.com>
> > > > Signed-off-by: Yi-De Wu <yi-de.wu at mediatek.com>
> > > > ---
> > > >  .../hypervisor/mediatek,geniezone-hyp.yaml    | 31
> > > > +++++++++++++++++++
> > > >  MAINTAINERS                                   |  1 +
> > > >  2 files changed, 32 insertions(+)
> > > >  create mode 100644
> > > > Documentation/devicetree/bindings/hypervisor/mediatek,geniezone
> > > > -
> > > > hyp.yaml
> > > > 
> > > 
> > > My bot found errors running 'make DT_CHECKER_FLAGS=-m
> > > dt_binding_check'
> > > on your patch (DT_CHECKER_FLAGS is new in v5.13):
> > > 
> > > yamllint warnings/errors:
> > > 
> > > dtschema/dtc warnings/errors:
> > > ./Documentation/devicetree/bindings/hypervisor/mediatek,geniezone
> > > -
> > > hyp.yaml: $id: relative path/filename doesn't match actual path
> > > or
> > > filename
> > >         expected:
> > > 
https://urldefense.com/v3/__http://devicetree.org/schemas/hypervisor/mediatek,geniezone-hyp.yaml*__;Iw!!CTRNKA9wMg0ARbw!joIOXbICM7UGvy3XBEJvfzSKO7s61efB87_NX5cqpUqpu5ot5cuzw50A8-8ledZT9_7ifsB2sKzxSD0$
> > > 
> > > doc reference errors (make refcheckdocs):
> > > 
> > > See
> > > 
https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20230428103622.18291-3-yi-de.wu@mediatek.com
> > > 
> > > The base for the series is generally the latest rc1. A different
> > > dependency
> > > should be noted in *this* patch.
> > > 
> > > If you already ran 'make dt_binding_check' and didn't see the
> > > above
> > > error(s), then make sure 'yamllint' is installed and dt-schema is
> > > up
> > > to
> > > date:
> > > 
> > > pip3 install dtschema --upgrade
> > > 
> > > Please check and re-submit after running the above command
> > > yourself.
> > > Note
> > > that DT_SCHEMA_FILES can be set to your schema file to speed up
> > > checking
> > > your schema. However, it must be unset to test all examples with
> > > your
> > > schema.
> > > 
> > 
> > Noted, we've run the yaml check and we are going to re-submit the
> > latest version in v3.
> > 
> > ************* MEDIATEK Confidentiality Notice ********************
> > The information contained in this e-mail message (including any
> > attachments) may be confidential, proprietary, privileged, or
> > otherwise
> > exempt from disclosure under applicable laws. It is intended to be
> > conveyed only to the designated recipient(s). Any use,
> > dissemination,
> > distribution, printing, retaining or copying of this e-mail
> > (including its
> > attachments) by unintended recipient(s) is strictly prohibited and
> > may
> > be unlawful. If you are not an intended recipient of this e-mail,
> > or believe
> > that you have received this e-mail in error, please notify the
> > sender
> > immediately (by replying to this e-mail), delete any and all copies
> > of
> > this e-mail (including any attachments) from your system, and do
> > not
> > disclose the content of this e-mail to any other person. Thank you!
> 
> Do you want us to reply w/ such a big confidentiality notice?
> 

My apology to this mistake, our mail server wasn't configured properly.
We've added all related mailing list to our disclaimer-free bypassing
list to prevent such issues from happening again.


More information about the linux-arm-kernel mailing list