All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Xi Ruoyao <xry111@xry111.site>
Cc: Huacai Chen <chenhuacai@kernel.org>,
	WANG Xuerui <kernel@xen0n.name>,
	Christophe Leroy <christophe.leroy@csgroup.eu>,
	linux-crypto@vger.kernel.org, loongarch@lists.linux.dev,
	linux-kernel@vger.kernel.org, Jinyang He <hejinyang@loongson.cn>,
	Tiezhu Yang <yangtiezhu@loongson.cn>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] LoongArch: vDSO: Tune the chacha20 implementation
Date: Mon, 23 Sep 2024 14:48:11 +0200	[thread overview]
Message-ID: <ZvFji_xpV0tWxZIn@zx2c4.com> (raw)
In-Reply-To: <b9bc6db245775b0a2e990467f414071e82b06a29.camel@xry111.site>

On Mon, Sep 23, 2024 at 04:06:41PM +0800, Xi Ruoyao wrote:
> On Mon, 2024-09-23 at 15:15 +0800, Huacai Chen wrote:
> > > +#define line3          state12, state13, state14, state15
> > > +
> > > +#define        line1_perm      state5, state6, state7, state4
> > > +#define        line2_perm      state10, state11, state8, state9
> > > +#define        line3_perm      state15, state12, state13, state14
> > > +
> > > +#define        copy            copy0, copy1, copy2, copy3
> > The indentation here is strange, it seems some of them are spaces and
> > some of them are tabs.
> 
> Oops indeed.  The tabs after "#define" should be a space instead.
> 
> Jason: can you edit it for me or do you want a new revision of the patch

I've fixed it in tree.

Jason

  reply	other threads:[~2024-09-23 12:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19  9:13 [PATCH] LoongArch: vDSO: Tune the chacha20 implementation Xi Ruoyao
2024-09-20 15:11 ` Jason A. Donenfeld
2024-09-23  7:15 ` Huacai Chen
2024-09-23  8:06   ` Xi Ruoyao
2024-09-23 12:48     ` Jason A. Donenfeld [this message]
2024-09-24  7:12       ` Huacai Chen

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=ZvFji_xpV0tWxZIn@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=arnd@arndb.de \
    --cc=chenhuacai@kernel.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=hejinyang@loongson.cn \
    --cc=kernel@xen0n.name \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=xry111@xry111.site \
    --cc=yangtiezhu@loongson.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.