From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Christoph Hellwig <hch@lst.de>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: dma_declare_coherent_memory and SuperH
Date: Wed, 23 Jun 2021 15:36:16 +0200 [thread overview]
Message-ID: <9d12d2e3-3faf-3b2f-0265-2baee85c3ead@physik.fu-berlin.de> (raw)
In-Reply-To: <20210623133205.GA28589@lst.de>
Hi Christoph!
On 6/23/21 3:32 PM, Christoph Hellwig wrote:
> I have a vague recollection that you were planning on dropping support
> for non-devicetree platforms, is that still the case?
I guess you are talking about this patch set [1].
Would be great if we could get this rebased and merged. Since Geert has access
to SH hardware as well, he might be able to help.
Adrian
> [1] https://lore.kernel.org/patchwork/cover/693910/
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2021-06-23 13:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 13:32 dma_declare_coherent_memory and SuperH Christoph Hellwig
2021-06-23 13:35 ` Geert Uytterhoeven
2021-06-23 13:36 ` John Paul Adrian Glaubitz [this message]
2021-06-26 22:36 ` Rob Landley
2021-06-26 22:38 ` Rob Landley
2021-06-28 13:38 ` Christoph Hellwig
2021-06-28 14:04 ` Rob Landley
2021-06-28 13:49 ` Christoph Hellwig
2021-06-28 14:29 ` Rob Landley
2021-06-28 16:33 ` Christoph Hellwig
2021-06-28 19:12 ` Geert Uytterhoeven
2021-06-28 19:47 ` Rob Landley
2021-06-27 3:08 ` Daniel Palmer
2021-06-27 8:33 ` John Paul Adrian Glaubitz
2021-06-28 8:57 ` Geert Uytterhoeven
2021-06-28 9:29 ` Daniel Palmer
2021-06-28 10:00 ` Geert Uytterhoeven
2021-06-28 14:29 ` Geert Uytterhoeven
2021-06-28 16:29 ` Christoph Hellwig
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=9d12d2e3-3faf-3b2f-0265-2baee85c3ead@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=dalias@libc.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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.