From: Krzysztof Kozlowski <krzk@kernel.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v6 1/2] dt-bindings: media: convert aspeed-video.txt to dt-schema
Date: Mon, 2 Sep 2024 08:57:30 +0200 [thread overview]
Message-ID: <3afc4f40-83ac-4ad1-be58-af33168273ac@kernel.org> (raw)
In-Reply-To: <TYZPR06MB65685EF88A548AEC26A54EC8F1922@TYZPR06MB6568.apcprd06.prod.outlook.com>
On 02/09/2024 03:44, Jammy Huang wrote:
> Hi Krzysztof,
>
>
> On 2024/8/29 ?? 03:56, Krzysztof Kozlowski wrote:
>>
>> On 29/08/2024 08:45, Jammy Huang wrote:
>>> Convert the ASPEED SoCs video txt bindings to dt-schema.
>>>
>>> Signed-off-by: Jammy Huang <jammy_huang@aspeedtech.com>
>>> ---
>>> .../bindings/media/aspeed,video-engine.yaml | 78
>> +++++++++++++++++++
>>> .../bindings/media/aspeed-video.txt | 33 --------
>>> 2 files changed, 78 insertions(+), 33 deletions(-) create mode
>>> 100644
>>> Documentation/devicetree/bindings/media/aspeed,video-engine.yaml
>>> delete mode 100644
>>> Documentation/devicetree/bindings/media/aspeed-video.txt
>>
>> Fix the paths in kernel (git grep).
> Sorry, I don't know exactly how to fix that.
> Do you mean I need to change the file name from 'drivers/media/platform/aspeed/aspeed-video.c'
> to ' drivers/media/platform/aspeed/aspeed-video-engine.c'???
No. You have warnings for stale paths.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-02 6:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 6:45 [PATCH v6 0/2] media: aspeed: Allow to capture from SoC display (GFX) Jammy Huang
2024-08-29 6:45 ` [PATCH v6 1/2] dt-bindings: media: convert aspeed-video.txt to dt-schema Jammy Huang
2024-08-29 7:55 ` Krzysztof Kozlowski
2024-09-02 1:44 ` Jammy Huang
2024-09-02 6:57 ` Krzysztof Kozlowski [this message]
2024-08-29 8:23 ` Rob Herring
2024-09-02 0:43 ` Jammy Huang
2024-08-30 0:21 ` kernel test robot
2024-08-29 6:45 ` [PATCH v6 2/2] media: aspeed: Allow to capture from SoC display (GFX) Jammy Huang
2024-08-29 7:56 ` Krzysztof Kozlowski
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=3afc4f40-83ac-4ad1-be58-af33168273ac@kernel.org \
--to=krzk@kernel.org \
--cc=linux-aspeed@lists.ozlabs.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