linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: ioremap and dma cleanups and fixes for superh (2nd resend)
Date: Tue, 14 Jul 2020 14:31:00 +0200	[thread overview]
Message-ID: <b0745e43-0ff1-58f7-70d5-60b9c8b8d81b@physik.fu-berlin.de> (raw)
In-Reply-To: <20200714121856.955680-1-hch@lst.de>

Hi Christoph!

On 7/14/20 2:18 PM, Christoph Hellwig wrote:
> can you take a look and possibly pick up the series below that untangles
> and sorts out minor issues with the sh ioremap and dma code?
> 
> I sent this out a few times, but never got an answer.  If you don't
> want to pick up the series I can also take it through one of my trees
> if I get ACKs.

Rich already said he is fine with most of the changes but we need to test
the DMA changes first to make sure they didn't break anything.

Thanks again for your continued efforts.

Adrian

-- 
 .''`.  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

  parent reply	other threads:[~2020-07-14 12:31 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14 12:18 ioremap and dma cleanups and fixes for superh (2nd resend) Christoph Hellwig
2020-07-14 12:18 ` [PATCH 01/10] sh: remove -Werror from Makefiles Christoph Hellwig
2020-07-14 12:18 ` [PATCH 02/10] sh: sort the selects for SUPERH alphabetically Christoph Hellwig
2020-07-14 12:18 ` [PATCH 03/10] sh: remove __KERNEL__ ifdefs from non-UAPI headers Christoph Hellwig
2020-07-14 12:18 ` [PATCH 04/10] sh: move ioremap_fixed details out of <asm/io.h> Christoph Hellwig
2020-07-14 12:18 ` [PATCH 05/10] sh: move the ioremap implementation out of line Christoph Hellwig
2020-07-14 12:18 ` [PATCH 06/10] sh: don't include <asm/io_trapped.h> in <asm/io.h> Christoph Hellwig
2020-07-14 12:18 ` [PATCH 07/10] sh: unexport register_trapped_io and match_trapped_io_handler Christoph Hellwig
2020-07-14 12:18 ` [PATCH 08/10] dma-mapping: consolidate the NO_DMA definition in kernel/dma/Kconfig Christoph Hellwig
2020-07-21  3:17   ` Rich Felker
2020-07-21  5:11     ` Christoph Hellwig
2020-07-22  0:43       ` Rich Felker
2020-07-14 12:18 ` [PATCH 09/10] sh: don't allow non-coherent DMA for NOMMU Christoph Hellwig
2020-08-28  2:00   ` Rich Felker
2020-08-28  2:11     ` Rich Felker
2020-08-28  4:24       ` Christoph Hellwig
2020-08-28  9:26         ` Ulf Hansson
2020-08-28 15:09           ` Rich Felker
2020-08-29  8:31             ` Christoph Hellwig
2020-08-31 11:28               ` Ulf Hansson
2020-07-14 12:18 ` [PATCH 10/10] sh: use the generic dma coherent remap allocator Christoph Hellwig
2020-07-14 12:31 ` John Paul Adrian Glaubitz [this message]
2020-07-14 15:59   ` ioremap and dma cleanups and fixes for superh (2nd resend) Rich Felker
2020-07-14 16:10     ` John Paul Adrian Glaubitz
2020-07-14 23:12       ` John Paul Adrian Glaubitz
2020-07-14 23:14         ` John Paul Adrian Glaubitz
2020-07-15  3:12         ` Rich Felker
2020-07-15  6:39           ` John Paul Adrian Glaubitz
2020-07-15  7:27         ` Geert Uytterhoeven
2020-07-15  7:37           ` John Paul Adrian Glaubitz
2020-07-15  8:06             ` Geert Uytterhoeven
2020-07-15  7:46           ` John Paul Adrian Glaubitz
2020-07-15  7:51             ` John Paul Adrian Glaubitz
2020-07-15  8:11               ` Geert Uytterhoeven
2020-07-15  8:27                 ` John Paul Adrian Glaubitz
2020-07-15 14:37                   ` John Paul Adrian Glaubitz
2020-07-15 15:39                     ` John Paul Adrian Glaubitz
2020-07-15 16:18                     ` John Paul Adrian Glaubitz
2020-07-15 18:21                       ` Geert Uytterhoeven
2020-07-15 18:27                         ` John Paul Adrian Glaubitz
2020-07-16  9:40                         ` Peter Zijlstra
2020-07-16 10:05                           ` John Paul Adrian Glaubitz
2020-07-16 10:29                           ` peterz
2020-07-16 10:54                             ` John Paul Adrian Glaubitz
2020-07-16 11:01                               ` peterz
2020-07-16 11:03                                 ` John Paul Adrian Glaubitz
2020-07-16 11:37                                   ` peterz
2020-07-16 12:04                                     ` peterz
2020-07-16 18:14                                       ` John Paul Adrian Glaubitz
2020-07-16 19:28                                         ` Peter Zijlstra
2020-07-16 19:33                                           ` John Paul Adrian Glaubitz
2020-07-16 11:30                       ` John Paul Adrian Glaubitz
2020-07-15  8:07             ` Geert Uytterhoeven
2020-07-16 11:31           ` John Paul Adrian Glaubitz
2020-07-20 13:38         ` Christoph Hellwig
2020-07-20 13:42           ` John Paul Adrian Glaubitz
2020-07-20 14:53             ` Rich Felker
2020-07-21  3:20               ` Rich Felker

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=b0745e43-0ff1-58f7-70d5-60b9c8b8d81b@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 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).