From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pavitrakumar Managutte <pavitrakumarm@vayavyalabs.com>
Cc: herbert@gondor.apana.org.au, robh@kernel.org,
linux-crypto@vger.kernel.org, Ruud.Derwig@synopsys.com,
manjunath.hadli@vayavyalabs.com, bhoomikak@vayavyalabs.com
Subject: Re: [PATCH 1/2] Device tree registration and property names changes
Date: Wed, 4 Sep 2024 09:53:39 +0200 [thread overview]
Message-ID: <0ea7694b-bda2-47d9-9778-9e68cef3d5d5@kernel.org> (raw)
In-Reply-To: <CALxtO0mREXjvGWYpL5PQUXAJ+v8yT9rHSOn69mfe7EMNz_LnmA@mail.gmail.com>
On 04/09/2024 09:41, Pavitrakumar Managutte wrote:
> Hi Krzysztof,
> Today's patch was an incremental fix on the SPAcc driver.
> Please ignore this as I am pushing the complete driver patchset with the
> DT bindings for review.
> SPAcc driver was reverted today since it was missing the DT bindings.
> I have addressed all your concerns in the SPAcc driver patchset which I
> will be pushing today.
So we wasted time reviewing this? I don't understand. Send finished
work or some finished stages, not something which you immediately
retract the moment people review it.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-09-04 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 3:11 [PATCH 1/2] Device tree registration and property names changes Pavitrakumar M
2024-09-04 3:11 ` [PATCH 2/2] SPAcc DT bindings Pavitrakumar M
2024-09-04 6:08 ` Krzysztof Kozlowski
2024-09-04 6:09 ` [PATCH 1/2] Device tree registration and property names changes Krzysztof Kozlowski
[not found] ` <CALxtO0mREXjvGWYpL5PQUXAJ+v8yT9rHSOn69mfe7EMNz_LnmA@mail.gmail.com>
2024-09-04 7:53 ` Krzysztof Kozlowski [this message]
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=0ea7694b-bda2-47d9-9778-9e68cef3d5d5@kernel.org \
--to=krzk@kernel.org \
--cc=Ruud.Derwig@synopsys.com \
--cc=bhoomikak@vayavyalabs.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=manjunath.hadli@vayavyalabs.com \
--cc=pavitrakumarm@vayavyalabs.com \
--cc=robh@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