devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Siddharth Menon <simeddon@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, andersson@kernel.org,
	krzk+dt@kernel.org,  conor+dt@kernel.org,
	baolin.wang@linux.alibaba.com,  linux-remoteproc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: hwlock: Convert to dtschema
Date: Thu, 20 Feb 2025 16:21:28 +0530	[thread overview]
Message-ID: <CAGd6pzMLQary4PYHN_7vc4xoS3SiAs_Rva+HymcXi_OFoGSakw@mail.gmail.com> (raw)
In-Reply-To: <20250218211200.GA991534-robh@kernel.org>

On Wed, 19 Feb 2025 at 02:42, Rob Herring <robh@kernel.org> wrote:
>
> The consumer side lives in dtschema already. Please add the provider
> side there too. Patches to devicetree-spec@vger.kernel.org or GH PR are
> fine.

Thank you and Krzysztof for the feedback, I shall address the issues in the
next patch set.

> For the descriptions, you'll need to relicense the text in hwlock.txt to
> dual GPL/BSD. You will need TI's permission for that.

Regarding the relicensing, should I first submit a patch to relicense
the hwlock.txt
binding, then follow up with a patch to replace it with the YAML file
and correct
incorrect paths?

Regards,
Siddharth Menon

      reply	other threads:[~2025-02-20 10:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 16:09 [PATCH] dt-bindings: hwlock: Convert to dtschema Siddharth Menon
2025-02-18 16:42 ` Krzysztof Kozlowski
2025-02-18 19:46 ` Rob Herring (Arm)
2025-02-18 21:12 ` Rob Herring
2025-02-20 10:51   ` Siddharth Menon [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=CAGd6pzMLQary4PYHN_7vc4xoS3SiAs_Rva+HymcXi_OFoGSakw@mail.gmail.com \
    --to=simeddon@gmail.com \
    --cc=andersson@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.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).