All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	linux-bluetooth@vger.kernel.org
Subject: Re: [1/2] dt-bindings: net: broadcom-bluetooth: Add CYW4373A0 DT binding
Date: Wed, 2 Nov 2022 11:33:27 -0500	[thread overview]
Message-ID: <20221102163327.GA4006397-robh@kernel.org> (raw)
In-Reply-To: <52c65cd1-9631-50a7-aded-7e4a877bbad9@denx.de>

On Tue, Nov 01, 2022 at 11:52:23PM +0100, Marek Vasut wrote:
> On 11/1/22 23:44, Luiz Augusto von Dentz wrote:
> > Hi Marek,
> 
> Hi,
> 
> > On Tue, Nov 1, 2022 at 3:38 PM Marek Vasut <marex@denx.de> wrote:
> > > 
> > > On 10/31/22 23:07, bluez.test.bot@gmail.com wrote:
> > > > This is automated email and please do not reply to this email!
> > > > 
> > > > Dear submitter,
> > > > 
> > > > Thank you for submitting the patches to the linux bluetooth mailing list.
> > > > This is a CI test results with your patch series:
> > > > PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=690631
> > > > 
> > > > ---Test result---
> > > > 
> > > > Test Summary:
> > > > CheckPatch                    PASS      2.99 seconds
> > > > GitLint                       PASS      1.48 seconds
> > > > SubjectPrefix                 FAIL      0.58 seconds
> > > 
> > > Should the DT bindings really have Bluetooth: prefix/tag too ?
> > > git log on prior art indicates they shouldn't .
> > 
> > If it is meant for bluetooth-next then yes it shall contain it since
> > the CI does attempt to check its presence, in the other hand we could
> > perhaps use the prefix [bluetooth] to avoid having the CI run on
> > patches that are not meant for bluetooth-next but I don't think other
> > subsystem do require this so it sort of hard to enforce proper
> > prefixing.
> 
> Linux Documentation/devicetree/bindings seems to start with dt-bindings:
> prefix always, so maybe we should keep it that way ?

Yes.

  reply	other threads:[~2022-11-02 16:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 20:48 [PATCH 1/2] dt-bindings: net: broadcom-bluetooth: Add CYW4373A0 DT binding Marek Vasut
2022-10-31 20:48 ` [PATCH 2/2] Bluetooth: hci_bcm: Add CYW4373A0 support Marek Vasut
2022-11-01 22:24   ` Linus Walleij
2022-10-31 22:07 ` [1/2] dt-bindings: net: broadcom-bluetooth: Add CYW4373A0 DT binding bluez.test.bot
2022-11-01 22:38   ` Marek Vasut
2022-11-01 22:44     ` Luiz Augusto von Dentz
2022-11-01 22:52       ` Marek Vasut
2022-11-02 16:33         ` Rob Herring [this message]
2022-11-01 22:20 ` [PATCH 1/2] " Linus Walleij
2022-11-01 22:39   ` Luiz Augusto von Dentz
2022-11-02 16:36     ` Rob Herring
2022-11-02 16:36 ` Rob Herring

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=20221102163327.GA4006397-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marex@denx.de \
    /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.