From: Conor Dooley <conor@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-riscv <linux-riscv@lists.infradead.org>,
Jisheng Zhang <jszhang@kernel.org>, Guo Ren <guoren@kernel.org>,
wefu@redhat.com
Subject: Re: linux-next: Tree for Jun 21 (riscv/errata/thead)
Date: Wed, 21 Jun 2023 19:41:42 +0100 [thread overview]
Message-ID: <20230621-sandal-jogger-5dd9618daa85@spud> (raw)
In-Reply-To: <ab38f6af-cb68-a918-1a63-2e7c927a8ffc@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 590 bytes --]
On Wed, Jun 21, 2023 at 11:40:31AM -0700, Randy Dunlap wrote:
> On 6/21/23 11:31, Conor Dooley wrote:
> > On Wed, Jun 21, 2023 at 11:25:14AM -0700, Randy Dunlap wrote:
> >> On 6/20/23 21:59, Stephen Rothwell wrote:
> >>> Hi all,
> >>>
> >>> Changes since 20230620:
> >>>
> >>
> >> on riscv 32-bit:
> >
> > Is XIP_KERNEL enabled? And if so, does this fix it?
>
> Yes. and Yes.
> Thanks.
>
> for your patch:
> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
> Tested-by: Randy Dunlap <rdunlap@infradead.org> # build-tested
Great, thanks Randy. I'll do the needful.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-06-21 18:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 4:59 linux-next: Tree for Jun 21 Stephen Rothwell
2023-06-21 18:25 ` linux-next: Tree for Jun 21 (riscv/errata/thead) Randy Dunlap
2023-06-21 18:31 ` Conor Dooley
2023-06-21 18:40 ` Randy Dunlap
2023-06-21 18:41 ` Conor Dooley [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=20230621-sandal-jogger-5dd9618daa85@spud \
--to=conor@kernel.org \
--cc=guoren@kernel.org \
--cc=jszhang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=wefu@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).