All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Wolfram Sang" <wsa+renesas@sang-engineering.com>,
	"linux-mmc @ vger . kernel . org" <linux-mmc@vger.kernel.org>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [RFC PATCH 0/2] mmc: tmio: further cleanups after kmap_atomic removal
Date: Wed, 02 Nov 2022 18:59:27 +0100	[thread overview]
Message-ID: <5b882121-f129-4130-bd5c-507072463a41@app.fastmail.com> (raw)
In-Reply-To: <20221102125430.28466-1-wsa+renesas@sang-engineering.com>

On Wed, Nov 2, 2022, at 13:54, Wolfram Sang wrote:
> Thanks to Adrian's patches mentioned in patch 1 in this series, we can
> now simplify the TMIO driver a tad further to ease future refactoring.
> This is marked as RFC because testing the corner cases is not so easy so
> extra eyes for review are more than welcome.
>
> Thanks and happy hacking!
>

Hi Wolfram,

I haven't posted my PXA boardfile patches yet, but after that
series, the separate tmio MFD devices (MFD_TMIO, MFD_ASIC3)
will all be gone, and tmio-mmc will only be used by SuperH,
Arm MACH_RENESAS and MACH_UNIPHIER. I hope this doesn't conflict
too much with your work and instead opens up further cleanups.

       Arnd

  parent reply	other threads:[~2022-11-02 18:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 12:54 [RFC PATCH 0/2] mmc: tmio: further cleanups after kmap_atomic removal Wolfram Sang
2022-11-02 12:54 ` [RFC PATCH 1/2] mmc: tmio: remove tmio_mmc_k(un)map_atomic helpers Wolfram Sang
2022-11-02 12:54 ` [RFC PATCH 2/2] mmc: tmio: remove 'alignment_shift' from platform data Wolfram Sang
2022-11-02 17:59 ` Arnd Bergmann [this message]
2022-11-02 18:58   ` [RFC PATCH 0/2] mmc: tmio: further cleanups after kmap_atomic removal Wolfram Sang
2022-11-18  9:45 ` Ulf Hansson

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=5b882121-f129-4130-bd5c-507072463a41@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.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 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.