Message ID | 20220307113529.315685-1-jonathanh@nvidia.com (mailing list archive) |
---|---|
State | Accepted |
Commit | 320689a1b543ca1396b3ed43bb18045e4a7ffd79 |
Headers | show |
Series | dt-bindings: spi: Fix Tegra QSPI example | expand |
On 07/03/2022 11:35, Jon Hunter wrote: > When running dt_binding_check on the nvidia,tegra210-quad.yaml binding > document the following error is reported ... > > nvidia,tegra210-quad.example.dt.yaml:0:0: /example-0/spi@70410000/flash@0: > failed to match any schema with compatible: ['spi-nor'] > > Update the example in the binding document to fix the above error. > > Signed-off-by: Jon Hunter <jonathanh@nvidia.com> I should have added ... Fixes: 9684752e5fe3 ("dt-bindings: spi: Add Tegra Quad SPI device tree binding") Jon
On Mon, Mar 07, 2022 at 11:35:29AM +0000, Jon Hunter wrote: > When running dt_binding_check on the nvidia,tegra210-quad.yaml binding > document the following error is reported ... Please submit patches using subject lines reflecting the style for the subsystem, this makes it easier for people to identify relevant patches. Look at what existing commits in the area you're changing are doing and make sure your subject lines visually resemble what they're doing. There's no need to resubmit to fix this alone.
On Mon, 7 Mar 2022 11:35:29 +0000, Jon Hunter wrote: > When running dt_binding_check on the nvidia,tegra210-quad.yaml binding > document the following error is reported ... > > nvidia,tegra210-quad.example.dt.yaml:0:0: /example-0/spi@70410000/flash@0: > failed to match any schema with compatible: ['spi-nor'] > > Update the example in the binding document to fix the above error. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/1] dt-bindings: spi: Fix Tegra QSPI example commit: 320689a1b543ca1396b3ed43bb18045e4a7ffd79 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark
diff --git a/Documentation/devicetree/bindings/spi/nvidia,tegra210-quad.yaml b/Documentation/devicetree/bindings/spi/nvidia,tegra210-quad.yaml index 6efea8970e62..0296edd1de22 100644 --- a/Documentation/devicetree/bindings/spi/nvidia,tegra210-quad.yaml +++ b/Documentation/devicetree/bindings/spi/nvidia,tegra210-quad.yaml @@ -107,7 +107,7 @@ examples: dma-names = "rx", "tx"; flash@0 { - compatible = "spi-nor"; + compatible = "jedec,spi-nor"; reg = <0>; spi-max-frequency = <104000000>; spi-tx-bus-width = <2>;
When running dt_binding_check on the nvidia,tegra210-quad.yaml binding document the following error is reported ... nvidia,tegra210-quad.example.dt.yaml:0:0: /example-0/spi@70410000/flash@0: failed to match any schema with compatible: ['spi-nor'] Update the example in the binding document to fix the above error. Signed-off-by: Jon Hunter <jonathanh@nvidia.com> --- Documentation/devicetree/bindings/spi/nvidia,tegra210-quad.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)