From: "Björn Töpel" <bjorn@kernel.org>
To: Conor Dooley <conor@kernel.org>, guoren@kernel.org
Cc: arnd@arndb.de, palmer@rivosinc.com, tglx@linutronix.de,
peterz@infradead.org, luto@kernel.org,
conor.dooley@microchip.com, heiko@sntech.de, jszhang@kernel.org,
lazyparser@gmail.com, falcon@tinylab.org, chenhuacai@kernel.org,
apatel@ventanamicro.com, atishp@atishpatra.org,
mark.rutland@arm.com, ben@decadent.org.uk,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org,
Guo Ren <guoren@linux.alibaba.com>
Subject: Re: [PATCH -next V15 0/7] riscv: Add GENERIC_ENTRY support
Date: Fri, 27 Jan 2023 10:15:30 +0100 [thread overview]
Message-ID: <877cx8tk25.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <Y9LTmmYuEWKNmyl2@spud>
Conor Dooley <conor@kernel.org> writes:
>> v15:
>> - Fixup compile error for !MMU (Thx Conor)
>> - Rebase on riscv for-next (20230127)
>
> nommu build looks fine now, thanks for fixing it up. Hopefully you're
> good to now now after 15 versions!
Yay! Would be great to see it end up in 6.3!
WARNING: multiple messages have this Message-ID (diff)
From: "Björn Töpel" <bjorn@kernel.org>
To: Conor Dooley <conor@kernel.org>, guoren@kernel.org
Cc: arnd@arndb.de, palmer@rivosinc.com, tglx@linutronix.de,
peterz@infradead.org, luto@kernel.org,
conor.dooley@microchip.com, heiko@sntech.de, jszhang@kernel.org,
lazyparser@gmail.com, falcon@tinylab.org, chenhuacai@kernel.org,
apatel@ventanamicro.com, atishp@atishpatra.org,
mark.rutland@arm.com, ben@decadent.org.uk,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org,
Guo Ren <guoren@linux.alibaba.com>
Subject: Re: [PATCH -next V15 0/7] riscv: Add GENERIC_ENTRY support
Date: Fri, 27 Jan 2023 10:15:30 +0100 [thread overview]
Message-ID: <877cx8tk25.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <Y9LTmmYuEWKNmyl2@spud>
Conor Dooley <conor@kernel.org> writes:
>> v15:
>> - Fixup compile error for !MMU (Thx Conor)
>> - Rebase on riscv for-next (20230127)
>
> nommu build looks fine now, thanks for fixing it up. Hopefully you're
> good to now now after 15 versions!
Yay! Would be great to see it end up in 6.3!
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-01-27 9:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 17:25 [PATCH -next V15 0/7] riscv: Add GENERIC_ENTRY support guoren
2023-01-26 17:25 ` guoren
2023-01-26 17:25 ` [PATCH -next V15 1/7] compiler_types.h: Add __noinstr_section() for noinstr guoren
2023-01-26 17:25 ` guoren
2023-01-26 19:14 ` Miguel Ojeda
2023-01-26 19:14 ` Miguel Ojeda
2023-01-27 1:55 ` Guo Ren
2023-01-27 1:55 ` Guo Ren
2023-01-26 17:25 ` [PATCH -next V15 2/7] riscv: ptrace: Remove duplicate operation guoren
2023-01-26 17:25 ` guoren
2023-01-26 17:25 ` [PATCH -next V15 3/7] riscv: entry: Add noinstr to prevent instrumentation inserted guoren
2023-01-26 17:25 ` guoren
2023-01-26 17:25 ` [PATCH -next V15 4/7] riscv: entry: Convert to generic entry guoren
2023-01-26 17:25 ` guoren
2023-01-26 17:25 ` [PATCH -next V15 5/7] riscv: entry: Remove extra level wrappers of trace_hardirqs_{on,off} guoren
2023-01-26 17:25 ` guoren
2023-01-26 17:25 ` [PATCH -next V15 6/7] riscv: entry: Consolidate ret_from_kernel_thread into ret_from_fork guoren
2023-01-26 17:25 ` guoren
2023-01-26 17:25 ` [PATCH -next V15 7/7] riscv: entry: Consolidate general regs saving/restoring guoren
2023-01-26 17:25 ` guoren
2023-01-26 19:25 ` [PATCH -next V15 0/7] riscv: Add GENERIC_ENTRY support Conor Dooley
2023-01-26 19:25 ` Conor Dooley
2023-01-27 9:15 ` Björn Töpel [this message]
2023-01-27 9:15 ` Björn Töpel
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=877cx8tk25.fsf@all.your.base.are.belong.to.us \
--to=bjorn@kernel.org \
--cc=apatel@ventanamicro.com \
--cc=arnd@arndb.de \
--cc=atishp@atishpatra.org \
--cc=ben@decadent.org.uk \
--cc=chenhuacai@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=falcon@tinylab.org \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=heiko@sntech.de \
--cc=jszhang@kernel.org \
--cc=lazyparser@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=palmer@rivosinc.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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.