Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pavitrakumar M <pavitrakumarm@vayavyalabs.com>,
	devicetree@vger.kernel.org, herbert@gondor.apana.org.au,
	linux-crypto@vger.kernel.org, robh@kernel.org
Cc: Ruud.Derwig@synopsys.com, manjunath.hadli@vayavyalabs.com,
	bhoomikak@vayavyalabs.com
Subject: Re: [PATCH v1 1/1] dt-bindings: crypto: Document support for SPAcc
Date: Thu, 5 Sep 2024 19:25:56 +0200	[thread overview]
Message-ID: <eb517a14-268a-4ee1-b330-0c440054e2b8@kernel.org> (raw)
In-Reply-To: <20240905150910.239832-2-pavitrakumarm@vayavyalabs.com>

On 05/09/2024 17:09, Pavitrakumar M wrote:
> Add DT bindings related to the SPAcc driver for Documentation.
> DWC Synopsys Security Protocol Accelerator(SPAcc) Hardware Crypto
> Engine is a crypto IP designed by Synopsys.
> 

<form letter>
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC (and consider --no-git-fallback argument). It might
happen, that command when run on an older kernel, gives you outdated
entries. Therefore please be sure you base your patches on recent Linux
kernel.

Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.
</form letter>

You already sent it... and now send again? That's like third time!
Version your patches and provide changelog under ---.


Anyway, this is just pointless without users. No explanation either. :/

I won't review it since you keep sending the same buggy code, without
changes.


Best regards,
Krzysztof


  reply	other threads:[~2024-09-05 17:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05 15:09 [PATCH v1 0/1] dt-bindings: crypto: Document support for SPAcc Pavitrakumar M
2024-09-05 15:09 ` [PATCH v1 1/1] " Pavitrakumar M
2024-09-05 17:25   ` Krzysztof Kozlowski [this message]
2024-09-05 18:23   ` Rob Herring
2024-09-05 19:28     ` Pavitrakumar Managutte
2024-09-05 20:17       ` Rob Herring
2024-09-06  6:58         ` Pavitrakumar Managutte

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=eb517a14-268a-4ee1-b330-0c440054e2b8@kernel.org \
    --to=krzk@kernel.org \
    --cc=Ruud.Derwig@synopsys.com \
    --cc=bhoomikak@vayavyalabs.com \
    --cc=devicetree@vger.kernel.org \
    --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