All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: "Clément Péron" <peron.clem@gmail.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
	wsa+renesas@sang-engineering.com, linux-mmc@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org,
	Avri Altman <avri.altman@wdc.com>
Subject: Re: [RFC PATCH 0/3] mmc: refactor RPMB block count handling
Date: Mon, 26 Nov 2018 10:38:58 +0100	[thread overview]
Message-ID: <20181126093858.GC921@kunai> (raw)
In-Reply-To: <CAJiuCcdLwC7OBLK5hEm6d07QkO6Z4Z_kOm70vXT8bZKs6QfXWQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 131 bytes --]


> Just want to point that RPMB with Iproc controller don't work on 4.14
> but it's not due to your patch.

Thanks, now I got it!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2018-11-26 20:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20 23:08 [RFC PATCH 0/3] mmc: refactor RPMB block count handling Wolfram Sang
2018-11-20 23:08 ` [RFC PATCH 1/3] mmc: core: validate user input for RPMB block count Wolfram Sang
2018-11-22 12:15   ` Avri Altman
2018-11-22 14:05     ` Wolfram Sang
2018-11-22 15:57       ` Avri Altman
2018-11-22 23:34         ` Wolfram Sang
2018-11-25 22:12   ` Clément Péron
2018-11-20 23:08 ` [RFC PATCH 2/3] mmc: core: use mrq->sbc when sending CMD23 for RPMB Wolfram Sang
2018-11-25 22:13   ` Clément Péron
2018-11-20 23:08 ` [RFC PATCH 3/3] mmc: core: remove obsolete mmc_set_blockcount() function Wolfram Sang
2018-11-25 22:13   ` Clément Péron
2018-11-21  0:31 ` [RFC PATCH 0/3] mmc: refactor RPMB block count handling Ulf Hansson
2018-11-21  2:35   ` Wolfram Sang
2018-11-22 10:35     ` Clément Péron
2018-11-24 14:26       ` Clément Péron
2018-11-24 21:37         ` Wolfram Sang
2018-11-25 22:11           ` Clément Péron
2018-11-26  9:38             ` Wolfram Sang [this message]

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=20181126093858.GC921@kunai \
    --to=wsa@the-dreams.de \
    --cc=avri.altman@wdc.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=peron.clem@gmail.com \
    --cc=ulf.hansson@linaro.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.