On Thu, Sep 21, 2023 at 05:24:57PM +0800, Jisheng Zhang wrote: > On Wed, Sep 20, 2023 at 09:36:19AM +0100, Conor Dooley wrote: > > Hey Jisheng, > > > > On Wed, Sep 13, 2023 at 04:44:18PM +0100, Conor Dooley wrote: > > > On Wed, Sep 13, 2023 at 11:15:57PM +0800, Jisheng Zhang wrote: > > > > On Tue, Sep 12, 2023 at 05:27:31PM +0100, Conor Dooley wrote: > > > > > On Tue, Sep 12, 2023 at 03:22:32PM +0800, Jisheng Zhang wrote: > > > > > > riscv select ARCH_DMA_DEFAULT_COHERENT by default, and th1520 isn't > > > > > > dma coherent, so set dma-noncoherent to reflect this fact. > > > > > > > > > > > > Signed-off-by: Jisheng Zhang <jszhang@xxxxxxxxxx> > > > > > > Tested-by: Drew Fustini <dfustini@xxxxxxxxxxxx> > > > > > > --- > > > > > > > > > > > > Since v1: > > > > > > - rebase on v6.6-rc1 > > > > > > - collect Tested-by tag > > > > > > > > > > Does this mean you're expecting me to take this? > > > > > > > > Hi Conor, > > > > > > > > I think I will take this and send PR to soc people. The reason > > > > I send v2 is the rebasing on new rc1 and v1 wasn't in linux-riscv > > > > mailist due to typo; > > > > > > Great, thanks. Please ask SFR to add your tree to linux-next. > > Hi Conor, > > I'm not sure how to do this. When MAINTAINERS patch is merged, send > an email to Stephen Rothwell, are these steps correct? Sorta, yeah. You don't need to have the MAINTAINERS patch merged first though, just send him a link to your tree and the branch name(s) & he will include it in linux-next. > > I lost my main x86 box over the weekend (looks like probably a dead > > motherboard), so I may have missed a response to this. > > > > Did you see this email? Additionally, can you add that git tree to the > > maintainers entry for the thead devicetrees? > > I just created a tree in > git://git.kernel.org/pub/scm/linux/kernel/git/jszhang/linux.git > > But it needs time for cgit to take place. I will send a patch > once it appears. Looks to be there for me now. Thanks for doing this!
Attachment:
signature.asc
Description: PGP signature
