From: David Gow <davidgow@google.com> To: Stephen Boyd <sboyd@kernel.org> Cc: Michael Turquette <mturquette@baylibre.com>, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, patches@lists.linux.dev, Brendan Higgins <brendan.higgins@linux.dev>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, "Rafael J . Wysocki" <rafael@kernel.org>, Richard Weinberger <richard@nod.at>, Anton Ivanov <anton.ivanov@cambridgegreys.com>, Johannes Berg <johannes@sipsolutions.net>, Vincent Whitchurch <vincent.whitchurch@axis.com>, Rob Herring <robh+dt@kernel.org>, Frank Rowand <frowand.list@gmail.com>, Christian Marangi <ansuelsmth@gmail.com>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, devicetree@vger.kernel.org, linux-um@lists.infradead.org, linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com Subject: Re: [PATCH 1/8] dt-bindings: Add linux,kunit binding Date: Fri, 3 Mar 2023 15:14:55 +0800 [thread overview] Message-ID: <CABVgOSkxOxpaHVtq1YpvNEshTZ3nic1p7NjV5DPdz066=tiS-A@mail.gmail.com> (raw) In-Reply-To: <20230302013822.1808711-2-sboyd@kernel.org> [-- Attachment #1: Type: text/plain, Size: 2087 bytes --] On Thu, 2 Mar 2023 at 09:38, Stephen Boyd <sboyd@kernel.org> wrote: > > Document the linux,kunit board compatible string. This board is loaded > into the Linux kernel when KUnit is testing devicetree dependent code. As with the series as a whole, this might need to change a little bit if we want to either use devicetree overlays and/or other architectures. That being said, I'm okay with having this until then: the only real topic for bikeshedding is the name. - Is KUnit best as a board name, or part of the vendor name? - Do we want to include the architecture in the name? Should it be "linux,kunit", "linux-kunit,uml", "linux,kunit-uml", etc? > > Cc: Rob Herring <robh+dt@kernel.org> > Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> > Cc: Brendan Higgins <brendan.higgins@linux.dev> > Cc: David Gow <davidgow@google.com> > Signed-off-by: Stephen Boyd <sboyd@kernel.org> > --- > .../bindings/kunit/linux,kunit.yaml | 24 +++++++++++++++++++ > 1 file changed, 24 insertions(+) > create mode 100644 Documentation/devicetree/bindings/kunit/linux,kunit.yaml > > diff --git a/Documentation/devicetree/bindings/kunit/linux,kunit.yaml b/Documentation/devicetree/bindings/kunit/linux,kunit.yaml > new file mode 100644 > index 000000000000..dfe6da4796e8 > --- /dev/null > +++ b/Documentation/devicetree/bindings/kunit/linux,kunit.yaml > @@ -0,0 +1,24 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/kunit/linux,kunit.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: KUnit > + > +maintainers: > + - Brendan Higgins <brendanhiggins@google.com> > + - David Gow <davidgow@google.com> > + > +description: > + KUnit board used to unit test the Linux kernel in User Mode Linux (UML). > + > +properties: > + $nodename: > + const: "/" > + compatible: > + const: linux,kunit > + > +additionalProperties: true > + > +... > -- > https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git/ > https://git.kernel.org/pub/scm/linux/kernel/git/sboyd/spmi.git > [-- Attachment #2: S/MIME Cryptographic Signature --] [-- Type: application/pkcs7-signature, Size: 4003 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: David Gow <davidgow@google.com> To: Stephen Boyd <sboyd@kernel.org> Cc: Michael Turquette <mturquette@baylibre.com>, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, patches@lists.linux.dev, Brendan Higgins <brendan.higgins@linux.dev>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, "Rafael J . Wysocki" <rafael@kernel.org>, Richard Weinberger <richard@nod.at>, Anton Ivanov <anton.ivanov@cambridgegreys.com>, Johannes Berg <johannes@sipsolutions.net>, Vincent Whitchurch <vincent.whitchurch@axis.com>, Rob Herring <robh+dt@kernel.org>, Frank Rowand <frowand.list@gmail.com>, Christian Marangi <ansuelsmth@gmail.com>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, devicetree@vger.kernel.org, linux-um@lists.infradead.org, linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com Subject: Re: [PATCH 1/8] dt-bindings: Add linux,kunit binding Date: Fri, 3 Mar 2023 15:14:55 +0800 [thread overview] Message-ID: <CABVgOSkxOxpaHVtq1YpvNEshTZ3nic1p7NjV5DPdz066=tiS-A@mail.gmail.com> (raw) In-Reply-To: <20230302013822.1808711-2-sboyd@kernel.org> [-- Attachment #1.1: Type: text/plain, Size: 2087 bytes --] On Thu, 2 Mar 2023 at 09:38, Stephen Boyd <sboyd@kernel.org> wrote: > > Document the linux,kunit board compatible string. This board is loaded > into the Linux kernel when KUnit is testing devicetree dependent code. As with the series as a whole, this might need to change a little bit if we want to either use devicetree overlays and/or other architectures. That being said, I'm okay with having this until then: the only real topic for bikeshedding is the name. - Is KUnit best as a board name, or part of the vendor name? - Do we want to include the architecture in the name? Should it be "linux,kunit", "linux-kunit,uml", "linux,kunit-uml", etc? > > Cc: Rob Herring <robh+dt@kernel.org> > Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> > Cc: Brendan Higgins <brendan.higgins@linux.dev> > Cc: David Gow <davidgow@google.com> > Signed-off-by: Stephen Boyd <sboyd@kernel.org> > --- > .../bindings/kunit/linux,kunit.yaml | 24 +++++++++++++++++++ > 1 file changed, 24 insertions(+) > create mode 100644 Documentation/devicetree/bindings/kunit/linux,kunit.yaml > > diff --git a/Documentation/devicetree/bindings/kunit/linux,kunit.yaml b/Documentation/devicetree/bindings/kunit/linux,kunit.yaml > new file mode 100644 > index 000000000000..dfe6da4796e8 > --- /dev/null > +++ b/Documentation/devicetree/bindings/kunit/linux,kunit.yaml > @@ -0,0 +1,24 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/kunit/linux,kunit.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: KUnit > + > +maintainers: > + - Brendan Higgins <brendanhiggins@google.com> > + - David Gow <davidgow@google.com> > + > +description: > + KUnit board used to unit test the Linux kernel in User Mode Linux (UML). > + > +properties: > + $nodename: > + const: "/" > + compatible: > + const: linux,kunit > + > +additionalProperties: true > + > +... > -- > https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git/ > https://git.kernel.org/pub/scm/linux/kernel/git/sboyd/spmi.git > [-- Attachment #1.2: S/MIME Cryptographic Signature --] [-- Type: application/pkcs7-signature, Size: 4003 bytes --] [-- Attachment #2: Type: text/plain, Size: 152 bytes --] _______________________________________________ linux-um mailing list linux-um@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2023-03-03 7:15 UTC|newest] Thread overview: 120+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-02 1:38 [PATCH 0/8] clk: Add kunit tests for fixed rate and parent data Stephen Boyd 2023-03-02 1:38 ` Stephen Boyd 2023-03-02 1:38 ` [PATCH 1/8] dt-bindings: Add linux,kunit binding Stephen Boyd 2023-03-02 1:38 ` Stephen Boyd 2023-03-03 7:14 ` David Gow [this message] 2023-03-03 7:14 ` David Gow 2023-03-03 7:49 ` Geert Uytterhoeven 2023-03-03 7:49 ` Geert Uytterhoeven 2023-03-09 23:12 ` Stephen Boyd 2023-03-09 23:12 ` Stephen Boyd 2023-03-10 7:55 ` David Gow 2023-03-10 7:55 ` David Gow 2023-03-02 1:38 ` [PATCH 2/8] of: Enable DTB loading on UML for KUnit tests Stephen Boyd 2023-03-02 1:38 ` Stephen Boyd 2023-03-03 7:15 ` David Gow 2023-03-03 7:15 ` David Gow 2023-03-09 23:19 ` Stephen Boyd 2023-03-09 23:19 ` Stephen Boyd 2023-03-10 8:09 ` David Gow 2023-03-10 8:09 ` David Gow 2023-03-10 23:34 ` Stephen Boyd 2023-03-10 23:34 ` Stephen Boyd 2023-03-11 6:42 ` David Gow 2023-03-11 6:42 ` David Gow 2023-03-13 16:02 ` Frank Rowand 2023-03-13 16:02 ` Frank Rowand 2023-03-14 4:28 ` Frank Rowand 2023-03-14 4:28 ` Frank Rowand 2023-03-15 7:04 ` David Gow 2023-03-15 7:04 ` David Gow 2023-03-15 21:35 ` Frank Rowand 2023-03-15 21:35 ` Frank Rowand 2023-03-16 0:45 ` Frank Rowand 2023-03-16 0:45 ` Frank Rowand 2023-03-16 4:15 ` David Gow 2023-03-16 4:15 ` David Gow 2023-03-21 20:56 ` Stephen Boyd 2023-03-21 20:56 ` Stephen Boyd 2023-03-08 19:46 ` Rob Herring 2023-03-08 19:46 ` Rob Herring 2023-03-02 1:38 ` [PATCH 3/8] kunit: Add test managed platform_device/driver APIs Stephen Boyd 2023-03-02 1:38 ` Stephen Boyd 2023-03-03 7:15 ` David Gow 2023-03-03 7:15 ` David Gow 2023-03-03 14:35 ` Maxime Ripard 2023-03-03 14:35 ` Maxime Ripard 2023-03-09 23:31 ` Stephen Boyd 2023-03-09 23:31 ` Stephen Boyd 2023-03-15 8:27 ` Maxime Ripard 2023-03-15 8:27 ` Maxime Ripard 2023-03-09 23:25 ` Stephen Boyd 2023-03-09 23:25 ` Stephen Boyd 2023-03-10 8:19 ` David Gow 2023-03-10 8:19 ` David Gow 2023-03-02 1:38 ` [PATCH 4/8] clk: Add test managed clk provider/consumer APIs Stephen Boyd 2023-03-02 1:38 ` Stephen Boyd 2023-03-03 7:15 ` David Gow 2023-03-03 7:15 ` David Gow 2023-03-10 23:21 ` Stephen Boyd 2023-03-10 23:21 ` Stephen Boyd 2023-03-11 6:32 ` David Gow 2023-03-11 6:32 ` David Gow 2023-03-21 14:32 ` Maxime Ripard 2023-03-21 14:32 ` Maxime Ripard 2023-03-02 1:38 ` [PATCH 5/8] dt-bindings: kunit: Add fixed rate clk consumer test Stephen Boyd 2023-03-02 1:38 ` Stephen Boyd 2023-03-02 1:38 ` [PATCH 6/8] clk: Add KUnit tests for clk fixed rate basic type Stephen Boyd 2023-03-02 1:38 ` Stephen Boyd 2023-03-02 1:38 ` [PATCH 7/8] dt-bindings: clk: Add KUnit clk_parent_data test Stephen Boyd 2023-03-02 1:38 ` Stephen Boyd 2023-03-02 1:38 ` [PATCH 8/8] clk: Add KUnit tests for clks registered with struct clk_parent_data Stephen Boyd 2023-03-02 1:38 ` Stephen Boyd 2023-03-02 8:13 ` [PATCH 0/8] clk: Add kunit tests for fixed rate and parent data David Gow 2023-03-02 8:13 ` David Gow 2023-03-02 17:32 ` Rob Herring 2023-03-02 17:32 ` Rob Herring 2023-03-02 19:27 ` Stephen Boyd 2023-03-02 19:27 ` Stephen Boyd 2023-03-02 19:47 ` Geert Uytterhoeven 2023-03-02 19:47 ` Geert Uytterhoeven 2023-03-05 3:32 ` Frank Rowand 2023-03-05 3:32 ` Frank Rowand 2023-03-05 9:26 ` Geert Uytterhoeven 2023-03-05 9:26 ` Geert Uytterhoeven 2023-03-06 5:32 ` Frank Rowand 2023-03-06 5:32 ` Frank Rowand 2023-03-04 15:04 ` Frank Rowand 2023-03-04 15:04 ` Frank Rowand 2023-03-07 21:53 ` Stephen Boyd 2023-03-07 21:53 ` Stephen Boyd 2023-03-04 14:48 ` Frank Rowand 2023-03-04 14:48 ` Frank Rowand 2023-03-02 17:13 ` Rob Herring 2023-03-02 17:13 ` Rob Herring 2023-03-02 19:44 ` Stephen Boyd 2023-03-02 19:44 ` Stephen Boyd 2023-03-02 20:18 ` Rob Herring 2023-03-02 20:18 ` Rob Herring 2023-03-02 23:57 ` Stephen Boyd 2023-03-02 23:57 ` Stephen Boyd 2023-03-04 15:39 ` Frank Rowand 2023-03-04 15:39 ` Frank Rowand 2023-03-06 12:53 ` Rob Herring 2023-03-06 12:53 ` Rob Herring 2023-03-06 15:03 ` Frank Rowand 2023-03-06 15:03 ` Frank Rowand 2023-03-04 15:37 ` Frank Rowand 2023-03-04 15:37 ` Frank Rowand 2023-03-04 15:33 ` Frank Rowand 2023-03-04 15:33 ` Frank Rowand 2023-03-03 14:38 ` Maxime Ripard 2023-03-03 14:38 ` Maxime Ripard 2023-03-07 22:37 ` Stephen Boyd 2023-03-07 22:37 ` Stephen Boyd 2023-03-04 15:50 ` Frank Rowand 2023-03-04 15:50 ` Frank Rowand 2023-03-10 7:48 ` David Gow 2023-03-10 7:48 ` David Gow 2023-03-13 15:30 ` Frank Rowand 2023-03-13 15:30 ` Frank Rowand
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='CABVgOSkxOxpaHVtq1YpvNEshTZ3nic1p7NjV5DPdz066=tiS-A@mail.gmail.com' \ --to=davidgow@google.com \ --cc=ansuelsmth@gmail.com \ --cc=anton.ivanov@cambridgegreys.com \ --cc=brendan.higgins@linux.dev \ --cc=devicetree@vger.kernel.org \ --cc=frowand.list@gmail.com \ --cc=gregkh@linuxfoundation.org \ --cc=johannes@sipsolutions.net \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=kunit-dev@googlegroups.com \ --cc=linux-clk@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-kselftest@vger.kernel.org \ --cc=linux-um@lists.infradead.org \ --cc=mturquette@baylibre.com \ --cc=patches@lists.linux.dev \ --cc=rafael@kernel.org \ --cc=richard@nod.at \ --cc=robh+dt@kernel.org \ --cc=sboyd@kernel.org \ --cc=vincent.whitchurch@axis.com \ /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: linkBe 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.