From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ryan Chen <ryan_chen@aspeedtech.com>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"sboyd@kernel.org" <sboyd@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"joel@jms.id.au" <joel@jms.id.au>,
"andrew@codeconstruct.com.au" <andrew@codeconstruct.com.au>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>
Subject: Re: [PATCH v2 1/3] dt-bindings: reset Add AST2700 reset bindings
Date: Wed, 28 Aug 2024 11:05:57 +0200 [thread overview]
Message-ID: <dae83777-bba6-4931-b5f1-dfe045d1a57d@kernel.org> (raw)
In-Reply-To: <OS8PR06MB7541FBC6591CD129D32B4A3DF2952@OS8PR06MB7541.apcprd06.prod.outlook.com>
On 28/08/2024 09:36, Ryan Chen wrote:
>> Subject: Re: [PATCH v2 1/3] dt-bindings: reset Add AST2700 reset bindings
>>
>> On 28/08/2024 08:27, Ryan Chen wrote:
>>> Add dt bindings for AST2700 reset driver.
>>>
>>> Signed-off-by: Ryan Chen <ryan_chen@aspeedtech.com>
>>> ---
>>> .../dt-bindings/reset/aspeed,ast2700-reset.h | 125
>>> ++++++++++++++++++
>>> 1 file changed, 125 insertions(+)
>>> create mode 100644 include/dt-bindings/reset/aspeed,ast2700-reset.h
>>
>> NAK.
>>
>> You still did not respond to my previous comments and did not implement
>> them.
>>
>> Month ago I told you this is not a separate patch.
>>
>> https://lore.kernel.org/all/e13c16db-e1a7-4ee0-867b-b184d421de7f@kernel
>> .org/
>>
> Sorry, I think your point is still two files, but it should be at 1 patch. am I right?
> If yes, I will put aspeed,ast2700-reset.h and aspeed,ast2700-clk.h to be 1 patch.
Binding headers are part of bindings patch.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-08-28 9:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 6:27 [PATCH v2 0/3] Add support for AST2700 clk driver Ryan Chen
2024-08-28 6:27 ` [PATCH v2 1/3] dt-bindings: reset Add AST2700 reset bindings Ryan Chen
2024-08-28 7:27 ` Krzysztof Kozlowski
2024-08-28 7:36 ` Ryan Chen
2024-08-28 9:05 ` Krzysztof Kozlowski [this message]
2024-08-28 6:27 ` [PATCH v2 2/3] dt-bindings: clock: Add AST2700 clock bindings Ryan Chen
2024-08-28 7:28 ` Krzysztof Kozlowski
2024-08-28 6:27 ` [PATCH v2 3/3] clk: aspeed: add AST2700 clk driver Ryan Chen
2024-08-28 7:30 ` Krzysztof Kozlowski
2024-08-28 7:39 ` Ryan Chen
2024-08-28 18:47 ` Stephen Boyd
2024-08-29 7:09 ` Ryan Chen
2024-08-29 17:50 ` Stephen Boyd
2024-08-30 7:50 ` Ryan Chen
2024-08-30 22:16 ` Stephen Boyd
2024-08-29 0:18 ` kernel test robot
2024-08-28 7:30 ` [PATCH v2 0/3] Add support for " Krzysztof Kozlowski
2024-08-29 6:23 ` 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=dae83777-bba6-4931-b5f1-dfe045d1a57d@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=ryan_chen@aspeedtech.com \
--cc=sboyd@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).