All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Guo Ren <guoren@kernel.org>
Cc: Andy Chiu <andy.chiu@sifive.com>,
	Conor Dooley <conor.dooley@microchip.com>,
	greentime.hu@sifive.com, vincent.chen@sifive.com,
	paul.walmsley@sifive.com, palmer@rivosinc.com,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	Guo Ren <guoren@linux.alibaba.com>
Subject: Re: [PATCH] riscv: vector: Fixup modules compile error
Date: Tue, 30 May 2023 17:04:14 +0100	[thread overview]
Message-ID: <20230530-static-smith-96cf543bfda2@spud> (raw)
In-Reply-To: <CAJF2gTR2fAkk1532VWmsWP5DSYN17ib80wa5QwwT=DC0LY9gGw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 265 bytes --]

On Tue, May 30, 2023 at 11:37:38PM +0800, Guo Ren wrote:
> I just found Linux-next build is broken, so I sent the patch. It seems
> you've solved that. That's okay.

Are you sure that linux-next is broken because of this?
This series should not be in linux-next...

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: Guo Ren <guoren@kernel.org>
Cc: Andy Chiu <andy.chiu@sifive.com>,
	Conor Dooley <conor.dooley@microchip.com>,
	greentime.hu@sifive.com, vincent.chen@sifive.com,
	paul.walmsley@sifive.com, palmer@rivosinc.com,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	Guo Ren <guoren@linux.alibaba.com>
Subject: Re: [PATCH] riscv: vector: Fixup modules compile error
Date: Tue, 30 May 2023 17:04:14 +0100	[thread overview]
Message-ID: <20230530-static-smith-96cf543bfda2@spud> (raw)
In-Reply-To: <CAJF2gTR2fAkk1532VWmsWP5DSYN17ib80wa5QwwT=DC0LY9gGw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 265 bytes --]

On Tue, May 30, 2023 at 11:37:38PM +0800, Guo Ren wrote:
> I just found Linux-next build is broken, so I sent the patch. It seems
> you've solved that. That's okay.

Are you sure that linux-next is broken because of this?
This series should not be in linux-next...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-05-30 16:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29  7:38 [PATCH] riscv: vector: Fixup modules compile error guoren
2023-05-29  7:38 ` guoren
2023-05-29 13:42 ` Conor Dooley
2023-05-29 13:42   ` Conor Dooley
2023-05-30  2:59   ` Guo Ren
2023-05-30  2:59     ` Guo Ren
2023-05-30  6:52     ` Guo Ren
2023-05-30  6:52       ` Guo Ren
2023-05-30  9:48       ` Andy Chiu
2023-05-30  9:48         ` Andy Chiu
2023-05-30 15:37         ` Guo Ren
2023-05-30 15:37           ` Guo Ren
2023-05-30 16:04           ` Conor Dooley [this message]
2023-05-30 16:04             ` Conor Dooley
2023-05-30 16:14             ` Guo Ren
2023-05-30 16:14               ` Guo Ren
2023-05-30 16:22               ` Guo Ren
2023-05-30 16:22                 ` Guo Ren

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=20230530-static-smith-96cf543bfda2@spud \
    --to=conor@kernel.org \
    --cc=andy.chiu@sifive.com \
    --cc=conor.dooley@microchip.com \
    --cc=greentime.hu@sifive.com \
    --cc=guoren@kernel.org \
    --cc=guoren@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@rivosinc.com \
    --cc=paul.walmsley@sifive.com \
    --cc=vincent.chen@sifive.com \
    /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.