All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Huacai Chen <chenhuacai@kernel.org>
To: Xi Ruoyao <xry111@xry111.site>
Cc: WANG Xuerui <kernel@xen0n.name>,
	loongarch@lists.linux.dev,  linux-kernel@vger.kernel.org,
	Tiezhu Yang <yangtiezhu@loongson.cn>
Subject: Re: [PATCH] LoongArch: Provide __lshrti3, __ashrti3, and __ashrti3
Date: Sat, 27 Apr 2024 16:39:38 +0800	[thread overview]
Message-ID: <CAAhV-H5bq-PONAfUYR8+5Q_z=7+1mqtXOGTsDi9g_r71qrf9Cw@mail.gmail.com> (raw)
In-Reply-To: <a3df8ae7ad7c4af447c6143858ae44c3da453704.camel@xry111.site>

On Sat, Apr 27, 2024 at 3:49 PM Xi Ruoyao <xry111@xry111.site> wrote:
>
> On Sat, 2024-04-27 at 15:20 +0800, Huacai Chen wrote:
> > > /* The prototypes are incorrect but this file is only used by
> > >     modpost which does not care.  */
> > > long long __ashlti3(long long a, int b);
> > > long long __ashrti3(long long a, int b);
> > > long long __lshrti3(long long a, int b);
> > >
> > > How do you think?
> > OK, then just keep the original status.
>
> Then I'll just send a patch squashing the origin version of this patch
> and the patch selecting ARCH_SUPPORTS_INT128 in a day if there are no
> other review comments.
Needn't, I will squash it when I apply.

Huacai
>
> --
> Xi Ruoyao <xry111@xry111.site>
> School of Aerospace Science and Technology, Xidian University

      reply	other threads:[~2024-04-27  8:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-26 12:14 [PATCH] LoongArch: Provide __lshrti3, __ashrti3, and __ashrti3 Xi Ruoyao
2024-04-27  2:50 ` Huacai Chen
2024-04-27  4:00   ` Xi Ruoyao
2024-04-27  4:13     ` Xi Ruoyao
2024-04-27  7:20       ` Huacai Chen
2024-04-27  7:49         ` Xi Ruoyao
2024-04-27  8:39           ` Huacai Chen [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='CAAhV-H5bq-PONAfUYR8+5Q_z=7+1mqtXOGTsDi9g_r71qrf9Cw@mail.gmail.com' \
    --to=chenhuacai@kernel.org \
    --cc=kernel@xen0n.name \
    --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.