From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Wolfram Sang" <wsa+renesas@sang-engineering.com>,
"Linux MMC List" <linux-mmc@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
"Masahiro Yamada" <yamada.masahiro@socionext.com>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>
Subject: Re: [RFC PATCH 2/2] mmc: renesas_sdhi: prevent overflow for max_req_size
Date: Fri, 15 Mar 2019 10:39:41 +0100 [thread overview]
Message-ID: <20190315093941.GC1176@kunai> (raw)
In-Reply-To: <CAMuHMdVEdU9CLSMzJWiDn5brc8bXNBemma=Zk4XtF4wsXHeb7Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 358 bytes --]
> > I am still confused. Which upper limit do you mean then? Because for
>
> TMIO_MAX_BLK_SIZE
>
> > blk_size and blk_count, they are both driver specific, or?
>
> Yes, they are driver-specific. So you cannot use a common upper limit.
And this is why I think my patch has a valid approach. But I am still
not sure I am getting your point.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-03-15 9:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 22:31 [RFC PATCH 0/2] mmc: renesas_sdhi: prevent overflow for max_req_size Wolfram Sang
2019-03-14 22:31 ` [RFC PATCH 1/2] mmc: tmio: introduce macro for max block size Wolfram Sang
2019-03-25 13:26 ` Ulf Hansson
2019-03-14 22:31 ` [RFC PATCH 2/2] mmc: renesas_sdhi: prevent overflow for max_req_size Wolfram Sang
2019-03-15 7:46 ` Geert Uytterhoeven
2019-03-15 8:29 ` Wolfram Sang
2019-03-15 8:49 ` Geert Uytterhoeven
2019-03-15 9:28 ` Wolfram Sang
2019-03-15 9:35 ` Geert Uytterhoeven
2019-03-15 9:39 ` Wolfram Sang [this message]
2019-03-15 9:46 ` Geert Uytterhoeven
2019-03-15 11:01 ` Wolfram Sang
2019-03-25 13:26 ` 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=20190315093941.GC1176@kunai \
--to=wsa@the-dreams.de \
--cc=geert@linux-m68k.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=wsa+renesas@sang-engineering.com \
--cc=yamada.masahiro@socionext.com \
--cc=yoshihiro.shimoda.uh@renesas.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.