Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Taehee Yoo <ap420073@gmail.com>
Cc: linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au,
	davem@davemloft.net, tglx@linutronix.de, mingo@redhat.com,
	dave.hansen@linux.intel.com, hpa@zytor.com,
	kirill.shutemov@linux.intel.com, richard@nod.at,
	viro@zeniv.linux.org.uk,
	sathyanarayanan.kuppuswamy@linux.intel.com, jpoimboe@kernel.org,
	elliott@hpe.com, x86@kernel.org, jussi.kivilinna@iki.fi,
	ebiggers@kernel.org
Subject: Re: [PATCH v6 0/4] crypto: aria: implement aria-avx2 and aria-avx512
Date: Mon, 21 Nov 2022 10:47:26 +0100	[thread overview]
Message-ID: <Y3tJLp3UlXGmK7HB@zn.tnic> (raw)
In-Reply-To: <20221121003955.2214462-1-ap420073@gmail.com>

On Mon, Nov 21, 2022 at 12:39:51AM +0000, Taehee Yoo wrote:
> This patchset is to implement aria-avx2 and aria-avx512.
> There are some differences between aria-avx, aria-avx2, and aria-avx512,
> but they are not core logic(s-box, diffusion layer).

From: Documentation/process/submitting-patches.rst

"Don't get discouraged - or impatient
------------------------------------

After you have submitted your change, be patient and wait.  Reviewers are
busy people and may not get to your patch right away.

Once upon a time, patches used to disappear into the void without comment,
but the development process works more smoothly than that now.  You should
receive comments within a week or so; if that does not happen, make sure
that you have sent your patches to the right place.  Wait for a minimum of
						     ^^^^^^^^^^^^^^^^^^^^^
one week before resubmitting or pinging reviewers - possibly longer during
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

busy times like merge windows."

IOW, pls stop spamming with your patchset.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  parent reply	other threads:[~2022-11-21  9:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-21  0:39 [PATCH v6 0/4] crypto: aria: implement aria-avx2 and aria-avx512 Taehee Yoo
2022-11-21  0:39 ` [PATCH v6 1/4] crypto: aria: add keystream array into request ctx Taehee Yoo
2022-11-21  0:39 ` [PATCH v6 2/4] crypto: aria: do not use magic number offsets of aria_ctx Taehee Yoo
2022-12-02 10:11   ` Herbert Xu
2022-12-03  5:01     ` Taehee Yoo
2022-11-21  0:39 ` [PATCH v6 3/4] crypto: aria: implement aria-avx2 Taehee Yoo
2022-11-21  0:39 ` [PATCH v6 4/4] crypto: aria: implement aria-avx512 Taehee Yoo
2022-11-21  9:47 ` Borislav Petkov [this message]
2022-11-21 11:20   ` [PATCH v6 0/4] crypto: aria: implement aria-avx2 and aria-avx512 Taehee Yoo

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=Y3tJLp3UlXGmK7HB@zn.tnic \
    --to=bp@alien8.de \
    --cc=ap420073@gmail.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=ebiggers@kernel.org \
    --cc=elliott@hpe.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=hpa@zytor.com \
    --cc=jpoimboe@kernel.org \
    --cc=jussi.kivilinna@iki.fi \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=richard@nod.at \
    --cc=sathyanarayanan.kuppuswamy@linux.intel.com \
    --cc=tglx@linutronix.de \
    --cc=viro@zeniv.linux.org.uk \
    --cc=x86@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