From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux MMC List <linux-mmc@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 6/6] mmc: renesas_sdhi: make 'dmac_only_one_rx' a quirk
Date: Fri, 1 Apr 2022 17:00:19 +0200 [thread overview]
Message-ID: <YkcTg8j9KCDXKvM9@ninjato> (raw)
In-Reply-To: <CAMuHMdWdtCsfVHYi4zqAMgN9wzDmwFpXs5VkJG4G0iXvuhSVKA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 132 bytes --]
> If there are no quirks (yes, we do have such systems ;-), this will
Wow, seems that slipped my reality :D Thanks for catching!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-04-01 15:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 12:30 [PATCH 0/6] mmc: renesas_sdhi: internal_dmac: updates after refactoring Wolfram Sang
2022-03-20 12:30 ` [PATCH 1/6] mmc: renesas_sdhi: remove outdated headers Wolfram Sang
2022-04-01 12:48 ` Geert Uytterhoeven
2022-03-20 12:30 ` [PATCH 2/6] mmc: renesas_sdhi: R-Car D3 also has no HS400 Wolfram Sang
2022-04-01 13:01 ` Geert Uytterhoeven
2022-04-01 14:59 ` Wolfram Sang
2022-04-01 15:08 ` Geert Uytterhoeven
2022-04-01 15:20 ` Wolfram Sang
2022-03-20 12:30 ` [PATCH 3/6] mmc: renesas_sdhi: make setup selection more understandable Wolfram Sang
2022-04-01 13:02 ` Geert Uytterhoeven
2022-03-20 12:30 ` [PATCH 4/6] mmc: renesas_sdhi: remove a stale comment Wolfram Sang
2022-04-01 13:03 ` Geert Uytterhoeven
2022-03-20 12:30 ` [PATCH 5/6] mmc: renesas_sdhi: make 'fixed_addr_mode' a quirk Wolfram Sang
2022-04-01 13:08 ` Geert Uytterhoeven
2022-03-20 12:30 ` [PATCH 6/6] mmc: renesas_sdhi: make 'dmac_only_one_rx' " Wolfram Sang
2022-04-01 14:13 ` Geert Uytterhoeven
2022-04-01 15:00 ` Wolfram Sang [this message]
2022-03-28 14:04 ` [PATCH 0/6] mmc: renesas_sdhi: internal_dmac: updates after refactoring 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=YkcTg8j9KCDXKvM9@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=geert@linux-m68k.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
/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