All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor.dooley@microchip.com>
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>,
	Conor Dooley <conor@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>
Subject: Re: linux-next: Tree for Aug 31 (riscv: ANDES errata)
Date: Fri, 1 Sep 2023 07:23:56 +0100	[thread overview]
Message-ID: <20230901-headed-unsigned-794833b7b5d5@wendy> (raw)
In-Reply-To: <33a5e278-fb4b-b5db-e4f6-bb5a1e4228ef@infradead.org>

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

On Thu, Aug 31, 2023 at 10:33:40PM -0700, Randy Dunlap wrote:
> 
> 
> On 8/30/23 20:55, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Please do *not* include material destined for v6.7 in your linux-next
> > included branches until *after* v6.6-rc1 has been released.  Also,
> > do *not* rebase you linu-next included branches onto v6.5.
> > 
> > Changes since 20230830:
> > 
> > The risc-v tree gained conflicts aginst Linus' tree.
> > 
> 
> On risc-v 32-bit or 64-bit, when CONFIG_MMU is not set:

lkp reported this yesterday too, Prabhakar is conjuring up a fix.

Thanks Randy for the report,
Conor.

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

WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor.dooley@microchip.com>
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>,
	Conor Dooley <conor@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>
Subject: Re: linux-next: Tree for Aug 31 (riscv: ANDES errata)
Date: Fri, 1 Sep 2023 07:23:56 +0100	[thread overview]
Message-ID: <20230901-headed-unsigned-794833b7b5d5@wendy> (raw)
In-Reply-To: <33a5e278-fb4b-b5db-e4f6-bb5a1e4228ef@infradead.org>


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

On Thu, Aug 31, 2023 at 10:33:40PM -0700, Randy Dunlap wrote:
> 
> 
> On 8/30/23 20:55, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Please do *not* include material destined for v6.7 in your linux-next
> > included branches until *after* v6.6-rc1 has been released.  Also,
> > do *not* rebase you linu-next included branches onto v6.5.
> > 
> > Changes since 20230830:
> > 
> > The risc-v tree gained conflicts aginst Linus' tree.
> > 
> 
> On risc-v 32-bit or 64-bit, when CONFIG_MMU is not set:

lkp reported this yesterday too, Prabhakar is conjuring up a fix.

Thanks Randy for the report,
Conor.

[-- 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

  reply	other threads:[~2023-09-01  6:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31  3:55 linux-next: Tree for Aug 31 Stephen Rothwell
2023-09-01  5:33 ` linux-next: Tree for Aug 31 (riscv: ANDES errata) Randy Dunlap
2023-09-01  5:33   ` Randy Dunlap
2023-09-01  6:23   ` Conor Dooley [this message]
2023-09-01  6:23     ` Conor Dooley

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=20230901-headed-unsigned-794833b7b5d5@wendy \
    --to=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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.